What is driving the MB of a stack?

[Phil Davis]

Hi David,

Another issue could be a resource fork. If you're on a Mac and have 
pasted a desktop icon into Finder's "About" box for the stack, that 
pasted image becomes one or more resources in the resource fork. If you 
delete the resources you don't want, stack bloat will decrease.

Here's a little tool you can use to review and remove resources from a 
resource fork:
https://www.dropbox.com/s/gxgxp35wfm53rz5/Resource%20Manager.livecode?dl=0

Phil Davis


On 4/29/15 7:07 AM, Scott Rossi wrote:
> 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
> 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"  <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
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>

-- 
Phil Davis