I've noticed that Arm Development Studio 2022.1 seems to have a fairly major memory leak, at least when running on Ubuntu 22.04.1 LTS.
When I launch it and just have an editor open, scrolling around and moving the cursor causes resident memory usage to keep going up - in one test I watched it go up to over 20 GB.
If I attach to a target and start debugging, I have maybe 5 minutes before all 128 GB memory is used up and the OOM reaper kills it.
I've just tested going back to Development Studio 2022.0 and it's much better: resident memory usage is around 3.5 GB, even when debugging an attached target.
I did a fresh install on a different machine yesterday, this time to debug a Juno R2 system via a DSTREAM-DT unit.
However, I just realized the memory leak happens even when _not_ connected to the target: just sitting there with a source file open, the memory usage continued to increase until the OOM killer got run.
[92666.736760] Out of memory: Killed process 114619 (armds_ide) total-vm:46630776kB, anon-rss:28654304kB, file-rss:0kB, shmem-rss:1076kB, UID:1000 pgtables:59492kB oom_score_adj:0
Hi RebeccaMy name is Stephen, and I'm an Arm colleague of Ronan.Thanks for reporting this. To help to narrow down or rule-out the cause of this, please could you try opening those files with the simple text editor in Eclipse, rather than using the default (context-sensitive) editor.
What type of files are you opening in the editor, e.g. C/C++/asm files?If these are C/C++ files, please could you also try using the default editor, but with indexing turned off (Window > Preferences > C/C++ > Indexer). Does that help?ThanksStephen
I'm opening C files: source from EDK2 or TF-A.
Disabling the indexer and opening the file using the simple text editor doesn't help.
Without opening the file, I can also make the leak occur by repeatedly clicking between the Project Explorer and the pane that shows "Source files will be opened in this space".
Please could you check if anything is being reported in the Error log? Use Window > Show View > Other, then open the Error Log view, and copy the first section of the log here. If Out Of Memory exception occurs, I think Eclipse asks to close the workbench. In that case, to collect the log, you can avoid closing the workbench or, alternatively, the log can be collected the next time you start Eclipse.
Also, if could you provide your IDE configuration details, that would be useful:
Hi again Rebecca
Looking more closely at your screenshots, there seem to be some rendering issues - black lines around the title of the tabs. They shouldn't be there, and we don't see them with our testing.
I'm wondering if this might be caused by the version of GTK 3 that you have installed on your Ubuntu 20.04 machine, or whether you are using VNC or X11 forwarding?
I'm using xrdp, so that might be why?
I deleted my ~/.arm, ~/developmentstudio-workspace and any eclipse-related directories I could see, and the memory leak appears to have stopped. I've been able to leave Development Studio running for over a day with no problems!
Ok, that's good news - thanks for letting us know :)