What is driving the MB of a stack?

[David Epstein]

Thanks to Scott Rossi for calling my attention to “unplaced groups,” which seem important enough to be better known.  I found and purged a few of these, but trimmed only a few KB off my 4.3 MB stack, which still seems much larger than its (known) content can explain.  Are there any other ways of diagnosing what’s going on?

David Epstein

> An issue that has been discussed in the past might be unplaced groups --
> groups that have been created at some time but aren't being used in the
> stack.  Here's one thread:
> <http://runtime-revolution.278305.n4.nabble.com/Storing-and-saving-a-settin <http://runtime-revolution.278305.n4.nabble.com/Storing-and-saving-a-settin>
> g-in-a-stand-alone-td4687858i40.html>
> 
> Regards,
> 
> Scott Rossi
> Creative Director
> Tactile Media, UX/UI Design
> 
> 
> 
> 
> On 4/29/15, 6:21 AM, "dfepstein at comcast.net <mailto:dfepstein at comcast.net>" <dfepstein at comcast.net <mailto:dfepstein at comcast.net>> wrote:
> 
>> A stack I have gradually improved over several years now occupies 4 MB on
>> disk, whereas for a long time it was more like 500 KB.
>> Is there some way to diagnose what elements are causing this?  I'd like
>> to generate a list of all of the stack's substacks, cards, fields,
>> images, scripts, etc., and see the amount of stack space each is
>> occupying. 
>> 
>> David Epstein