×
INDI Library v1.8.6 Released (21 Aug 2020)

August 2020 release of INDI Library v1.8.6 introduces new drivers while providing fixes and improvements to existing devices and core framework.

Possible Memory Leak in Kstars

1 year 2 weeks ago
Vamosi
Fresh Boarder
Fresh Boarder
Posts: 14
More
Topic Author
Possible Memory Leak in Kstars #42921
Hi Jasem,

When Imaging last night, I have ran into what seems like a memory leak issue with kstars. My imaging sequence stopped with an out of memory error. I am on a Raspberry Pi 4 4GB model, with zram installed. KStars is version 3.3.5, runnning on Raspbian, compiled from code. I had to stop just a couple minutes ago, because it almost ran out of memory again, also as seen on the attached pictures I have closed kstars, and the ram consumption is basically the same. My log is full because of the other issue discussed earlier with the qhy camera, it's over 2gb for 2 hours of imaging. Can the QHY camera cause this issue maybe? If not, is it possible I messed up something when compiling.? Also can I do something, so that my log doesn't get spammed this much with QHY entries other than disabling verbose logging?

Also I am running on Raspbian, because however hard I try with Ubuntu, after starting Ekos, the whole system crashes, for no apparent reason exactly 3 minutes after connection to my real hardware, with no log entries. It doesn't do this when connecting simulators, and I could replicate it on 4 different Ubuntu installs. I am guessing it's either the QHY driver or my QHY camera. Lets see if you maybe have a solution, but I think I might have to reinstall.

Thanks!
Florian


Hetes Astronomical Observatory (under construction)

Sky-Watcher Quattro 10CF 10" f/4 or Sky-Watcher 150P 6" f/5 with ZWO ASI 183MM PRO, ZWO 8x1,25 EFW,
ZWO ASI 290MM Mini and OAG on Sky-Watcher AZ-EQ6 GT with EKOS on Raspberry Pi 4

Sky-Watcher Esprit 80ED with Canon 600D and Lacerta M-gen
Attachments:

Please Log in or Create an account to join the conversation.

1 year 2 weeks ago
AstroNerd
Moderator
Moderator
Posts: 852
Karma: 1
More
Possible Memory Leak in Kstars #42935
Have you tried the new Beta Stellarmate for the the rpi4, or just bare Ubuntu mate, as that does not work...

Stellarmate OS on Raspberry pi4b
Skywatcher EQ8 pro, on steel pier
Takahashi FSQ85 & Meade 8” SCT (de-forked)
Starlight Xpress SXVR H18, SXVR M25c, Lodestar x2 Guide Camera
Pegasus Ultimate Hub V2 for all USB & Power
Pegasus focus motors on both scopes

Please Log in or Create an account to join the conversation.

1 year 2 weeks ago
knro
Administrator
Administrator
Posts: 8379
Karma: 51
Possible Memory Leak in Kstars #42948
Can you run KStars in gdb? so that when it crashes, we can at least get a backtrace?
gdb -ex run kstars

For the memory issue, try to disable logging. Then monitor RAM, do you see it increasing steadily? Find out which driver is causing this.

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info

Please Log in or Create an account to join the conversation.

10 months 1 week ago
El Corazon
Platinum Boarder
Platinum Boarder
Posts: 847
Karma: 3
More
Possible Memory Leak in Kstars #45612

knro wrote: Can you run KStars in gdb? so that when it crashes, we can at least get a backtrace?

<code>
gdb -ex run kstars
</code>

For the memory issue, try to disable logging. Then monitor RAM, do you see it increasing steadily? Find out which driver is causing this.



I also have frequent crashes on the RPi4 only. The last one appears to have been caused by gphoto2.

As for the "memory leak" Vamosi is seeing, I am wondering whether Buster lumps together used, shared and cached memory. My system monitor (using MATE) in the tray also shows memory maxed out, but most of that is used by the cache. When I open System Monitor, actually memory use is shown correctly. Also, when using free -m in the Terminal, most of the memory is used by the cache.
I am wondering whether the increased memory use reflects numerous open FITS windows? Turning off FITS viewer or checking the 'single FITS viewer window' box in EKOS might resolve that problem.

Atlas Pro AZ-EQ, ASI1600MM-Pro, ASI120MM-S, ES102ED, WO-Z61, Nikon D3300, ASI-EFW, ZWO LRGB,Ha,O3,S2 filter set

Please Log in or Create an account to join the conversation.

10 months 1 week ago
werper
Expert Boarder
Expert Boarder
Posts: 87
Karma: 2
More
Possible Memory Leak in Kstars #45614
FWIW: I'm also running a RPi 4, 4GB. SM OS 1.4.3 seems to run FLAWLESSLY with my hardware: iOptron iEQ45 Pro mount, Canon T3i DSLR, Lodestar X2 guide cam, RoboFocus auto-focuser, astrromtry. I run Kstars/Ekos on an older Dell I5, connecting to SM via WiFi Hotspot mode. SM OS 1.4.4 gave me nothing but problems with WiFi connectivity issues so I went back to 1.4.3.

TPO 8" Ritchey-Chretien Astrograph
Moonlite CS focuser with Motor Drive
RoboFocus Auto Focuser
iOptron iEQ45 Pro Mount on Tripier
Stellarrmate OS RPi 4, 4GB
ZWO ASI533MC Pro
Starlight Xpress Lodestar X2 Guide Cam
Astromania 60 Guide Scope
Polemaster Polar Alignment Cam

Please Log in or Create an account to join the conversation.

9 months 4 weeks ago
Lead_weight
Gold Boarder
Gold Boarder
Posts: 455
Karma: 4
More
Possible Memory Leak in Kstars #46211
I'm running into the memory leak too. I'm on a RPi4 with Stellarmate 1.45 (just did a clean install tonight). I also have all the updates installed. The INDI server shuts down and EKOS stops taking images. Memory use is at 94%.

-Andrew
––––––––––
Mac Observatory - All about using the Mac for Astrophotography: www.macobservatory.com
Astrobin: www.astrobin.com/users/Lead_Weight/

Please Log in or Create an account to join the conversation.

9 months 4 weeks ago
wotalota
Gold Boarder
Gold Boarder
Posts: 184
More
Possible Memory Leak in Kstars #46227
Would it not be normal for most all the memory to be used up on these small systems? Memory management would attempt to put it to use and be depending on having enough swap space defined on disk.

Mach1, TS86SDQ, ASI071, ASI174, OAG, focusPro

Please Log in or Create an account to join the conversation.

Time to create page: 0.550 seconds