[bug] strange memory leak in LC
Sean Cole (Pi)
sean at pidigital.co.uk
Fri Mar 26 09:01:54 EDT 2021
Wow, Andre, that's impressive. That amounts to about 34MB per minute over
48hrs. I've had a pretty massive stack (226MB file at the moment) on my Mac
sitting here over the last week. Looking in the activity monitor, LC has
987MB associated with it. and watching it over a period of time it remains
stable and even went down a tiny bit.
I wonder if this is more an issue with Rosetta2 in this instance. Maybe
something in LC leaks because of the Rosetta transformation of the binary.
Perhaps, as a test, open the same stack on a non-AppleSilicon Mac and watch
them both for how much memory they expend over a period of time.
All the best with that.
On Fri, 26 Mar 2021 at 10:03, Andre Garzia via use-livecode <
use-livecode at lists.runrev.com> wrote:
> I have no idea what happened. I’m running LC 9.6.2-rc-3 on macOS Big Sur
> on M1 ISA (so it is running under Rosetta 2). I kept the IDE opened for a
> couple days, I was working on a gaziliion stacks at the same time and was
> not yet ready to close them.
> The stacks were not doing anything, they were not running “send in time”
> commands or doing any kind of processing, they were just opened. Then macOS
> showed me a dialog I have never ever seen on macOS 10.x, a memory
> exhaustion dialog. Looking closer at it, LiveCode was using 100 GB of
> memory, as in Gigabyte, as can be seen on this screenshot:
> http://andregarzia.com/img/shots/lc-memory-leak.png <
> I remember things like the “default button” causing leaks due to the
> animation and so on, but all I had was a bunch of custom stacks open and
> the script editor focused. Thats it. It was open since yesterday.
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode