×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Memory Leak

  • Posts: 4
  • Thank you received: 0

Replied by Tim Schuh on topic Memory Leak

Every 10 frames in a series of 30 subs. There was a previous run of 10 subs so I'm already starting with a bit of memory load.

stellarmate@stellarmate:~$ ps auxww | grep kstars
Start: stellar+  1301  1.0 36.9 2959744 1372704 ?     SLl  11:20   6:49 /usr/bin/kstars --paused
10 subs: stellar+  1301  1.1 45.5 3280028 1691824 ?     SLl  11:20   7:18 /usr/bin/kstars --paused
20 subs: stellar+  1301  1.2 54.1 3600308 2012224 ?     SLl  11:20   7:43 /usr/bin/kstars --paused
30 subs: stellar+  1301  1.2 62.4 3920592 2317312 ?     SLl  11:20   8:07 /usr/bin/kstars --paused
 
stellarmate@stellarmate:~$ sudo dpkg --list | grep kstars
ii  kstars-bleeding                               6:3.3.9+202001011609~ubuntu18.04.1        arm64        desktop planetarium for KDE
ii  kstars-bleeding-data                          6:3.3.9+202001011609~ubuntu18.04.1        all          data files for KStars desktop planetarium
ii  kstars-bleeding-dbg                           6:3.3.9+202001011609~ubuntu18.04.1        arm64        debug information for the desktop planetarium for KDE
 
stellarmate@stellarmate:~$ sudo dpkg --list | grep qhy
ii  indi-qhy                                      2.6~202001021211~ubuntu18.04.1            arm64        INDI QHY Driver. This driver is compatible with any INDI client such as KStars or Xephem.
ii  libqhy                                        6.0.5+unstable~201912300954~ubuntu18.04.1 arm64        libqhy provide libraries to access and control QHY CCDs and Filter Wheels.


Disconnecting the gear and stopping the server made no difference of course. Memory is freed immediately upon kstars exiting. 30-ish subs are about all I can get before exhausting the 4GB RPi4.
Last edit: 4 years 3 months ago by Tim Schuh.
4 years 3 months ago #48032

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

  • Posts: 19
  • Thank you received: 1

Replied by Jim Johnston on topic Memory Leak

New to this forum and to the whole K-Stars and Ekos thing. I have also been experiencing this memory leak problem; I screen recorded my session this evening and have posted a link here if anyone is interested. K-Stars crashed at 1:14:23 in this clip. I has the FITS viewer disabled in K-Stars. I am running on a Raspberry Pi 4 with 4GB RAM and Astroberry.

www.dropbox.com/s/anp7k2o25f0jovh/ice_vi...201-181546.webm?dl=0

Jim
4 years 2 months ago #48844

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

  • Posts: 1119
  • Thank you received: 182

Replied by Jose Corazon on topic Memory Leak

There is not file that is accessible. Can you please repost?
I also have these repeated and absolutely unpredictable crashes, but only on my Pi4. Never on my mini-PC, so I suspect this is something inherent to the Pi4 firmware or the architecture.
4 years 2 months ago #48883

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

  • Posts: 398
  • Thank you received: 117

Replied by Doug S on topic Memory Leak

For another data point, I don't see the problem with simulation at all. I ran last night with real hardware (SM OS, Pi4-4GB, ASI183mc Pro, ASI290mm Mini) and saw a crash every time I ran any sequence containing multiple image captures. I do get a single fits preview (haven't turned that off yet). However, when I ran with only 1 capture at a time (no matter how many times I ran a single capture), it always worked fine. I ran out of time last night during my tests, but I was curious about whether a zero delay between image captures could be aggravating the situation. I upgraded to 3.4 today, and I'll try again tonight to capture some additional data and post here on whether this is better in the new release.
Last edit: 4 years 2 months ago by Doug S. Reason: spelling error
4 years 2 months ago #48886

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

  • Posts: 1119
  • Thank you received: 182

Replied by Jose Corazon on topic Memory Leak

A few observations that might help with this:
1) I think you hit an important point with the 'exposure delay' . Adding 5 s between exposures has reduced crashes for me.
2) I have FAR fewer crashes (but not 0) when I run the Pi4 from an SSD with Swap enabled instead of from an SD card. The SD card is S-L-O-W and probably aggravates the data congestion the Pi4 can't handle.
3) FITS viewer on or off makes no difference for me.
4 years 2 months ago #48887

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

  • Posts: 1222
  • Thank you received: 565

Replied by Hy Murveit on topic Memory Leak

When you say crashes, do you mean memory leak (running out of memory) crashes, or any crashes (eg. standard memory corruption), or is it hard to tell?

So, is you're suspicion that it has to do with the saving of the file?

Are you talking about a fits camera, or a DSLR? A mono camera or an RGB camera?

Hy
4 years 2 months ago #48889

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

  • Posts: 1119
  • Thank you received: 182

Replied by Jose Corazon on topic Memory Leak

With 'crash' I mean Kstars quitting abruptly without any warning and the screen reverting to the Desktop. The few times I saw it happen, I did not see the memory maxing out. I have posted a few logs here before and the logs are interesting inasmuch the log is literally cut off in mid-sentence, even mid-word. The logger was writing normally, no warning and then - finito. Happened to me with DSLR, OSC and monochrome cameras.
I can't recognize a pattern. In fact, the same setup, no change in hardware or software updates, would run flawlessly through the night yesterday and record 500 frames, only to crash after 100 frames today.
And that only happens on the Pi4, my mini-PC (also with only 4GB RAM) runs just fine through the night.
Definitely Pi4 specific.
4 years 2 months ago #48892

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

  • Posts: 398
  • Thank you received: 117

Replied by Doug S on topic Memory Leak

I'm using an OSC ASI183mc Pro. The crash drops at least the hotspot, and I think more because when the VNC connection retry succeeds, KStars and Ekos are completely gone and need to be restarted. I do have my suspicions about the file save....that's what led me to wonder about inserting a delay. The camera produces 40MB files. So, I will add a delay and see if I can reduce this as El Corazon suggests....
4 years 2 months ago #48895

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

  • Posts: 1119
  • Thank you received: 182

Replied by Jose Corazon on topic Memory Leak

I'm not using hotspot mode, my Pi4 is connected to my home WiFi and VNC is NOT dropped when this occurs.
But I concur with the rest of your description: Kstars and Ekos windows are gone, only the desktop is visible.
I have not extended the delay beyond 5s, perhaps that increases stability further? I am using the 183MM Pro, so basically same camera, same file size. Also happens with the ASI1600MM, which writes slightly smaller files (32 MB).
Last edit: 4 years 2 months ago by Jose Corazon.
4 years 2 months ago #48896

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

  • Posts: 19
  • Thank you received: 1

Replied by Jim Johnston on topic Memory Leak

Sorry; posted it on YouTube instead:
4 years 2 months ago #48900

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

  • Posts: 398
  • Thank you received: 117

Replied by Doug S on topic Memory Leak

From tests tonight, I wasn't able to reproduce last night's consistent failures. This was after applying the new release. I now seem able to take large sets of 40Mb subs without any delay and the SW doesn't crumble. I didn't do an extreme exhaustive test, but this release does seem more stable than the prior release for these large format ASI cams. I had lots of other issues (my own equip), but the SW was good tonight. Let's hope it's a good sign!
4 years 2 months ago #48921

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

  • Posts: 1119
  • Thank you received: 182

Replied by Jose Corazon on topic Memory Leak

Don't hold your breath just yet. I have never had the failures you describe, not being able to string more than a single exposure together, but I have had crashes after 50, 100 or even 300 perfectly captured frames. There does not seem to be a rhyme or reason to it. It just happens as in Stargazer's video (previous post). All is well and from one split second to the next, Kstars has crashed. It has nothing to do with the release. I have had that ever since I started using the Pi4.
I wish there were a clear path to figuring out what the problem is.
4 years 2 months ago #48923

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

Time to create page: 0.438 seconds