Summary: | Ekos eating ram. | ||
---|---|---|---|
Product: | [Applications] kstars | Reporter: | Ray Wells 4.0 <blues_hawk> |
Component: | general | Assignee: | Jasem Mutlaq <mutlaqja> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 2.9.8 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Ray Wells 4.0
2018-10-23 21:44:55 UTC
Ok I can confirm this. However, after a LOT of digging around yesterday I wasn't able to locate the leak. I made few changes in GIT to make it better, but when I checked it with tools like heaptrack, I can see FITSView creating (and then destroying) QImage and memory consumption goes back to normal (~120MB), but htop still shows the memory as RES and indeed it doesn't go down even after using delete[] The weird thing as well is that memory allocation itself doesn't seem to increase RES up until the data is _read_ into the array.. not sure what's going on here either. Please check with KStars 3.3.4 Just saw this in my email. I'll add it to my agenda. Last time I used the 178mm was in July and it did not run out of ram, but I've been playing with filters and doing very long exposures which results in fewer frames. The Pentax K5 I've been using lately is too slow to see the leak easily. I'll make a note to keep a sharp eye on it next time I use the asi178mm camera and put a lum filter back in the wheel. Feel free to remind me if I forget... (never happens--snork) Ray Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Arg... I'm making a note and will set up a quick test when I get home. Yes. I can confirm the memory leak is now well plugged. In fact even running two ASI cameras with guiding and focus module in framing mode Kstars now releases ram surprisingly well, often moving as high at 5% before releasing back to ~.3% Mission, Complete. Thanks Jasem. :D |