×

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

Bi-monthly release with minor bug fixes and improvements

KStars fails to allocate memory and crashes after capturing a couple of images.

  • Posts: 1
  • Thank you received: 0
Hi guys,

I've updated to version 3.5.7 Stable on RPi4 with 4G RAM running Raspbian GNU/Linux 10 (buster).

The issue is that while capturing images the allocated memory by KStars increases by every captured image and after a while there is no more memory and the app crashes with the message: /home/astroberry/DEV/BUILD/indi/libs/lilxml.c(moremem): Failed to allocate memory.
Segmentation fault.

Here is the end of log file:
[2022-03-05T22:03:52.520 CET INFO ][   org.kde.kstars.ekos.capture] - "Capturing 1.000-second  image..."
[2022-03-05T22:03:52.578 CET DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MM Pro : "[DEBUG] StartExposure->setexp : 1.000s "
[2022-03-05T22:03:55.204 CET DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MM Pro : "[DEBUG] Uploading file. Ext: fits, Size: 93559680, sendImage? Yes, saveImage? No "
[2022-03-05T22:03:58.511 CET DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MM Pro : "[DEBUG] BLOB transfer took 1.24188 seconds "
[2022-03-05T22:03:58.511 CET DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MM Pro : "[DEBUG] Upload complete "
[2022-03-05T22:03:58.512 CET DEBG ][           org.kde.kstars.indi] - Image received. Mode: "Normal" Size: 93559680
[2022-03-05T22:03:58.579 CET INFO ][           org.kde.kstars.indi] - "FITS" file saved to "/home/pi/Pictures/Light/Lum/Light_Lum_1_secs_2022-03-05T22-03-58_008.fits"
[2022-03-05T22:04:00.817 CET INFO ][   org.kde.kstars.ekos.capture] - "Received image 3 out of 10."
[2022-03-05T22:04:06.024 CET INFO ][   org.kde.kstars.ekos.capture] - "Captured /home/pi/Pictures/Light/Lum/Light_Lum_1_secs_2022-03-05T22-03-58_008.fits"
[2022-03-05T22:04:07.846 CET DEBG ][           org.kde.kstars.indi] - INDI Server:  "2022-03-05T21:04:07: Driver indi_asi_wheel: Unknown transfer code: #1 LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED"
[2022-03-05T22:04:07.846 CET DEBG ][           org.kde.kstars.indi] - INDI Server:  ""
[2022-03-05T22:04:07.848 CET INFO ][   org.kde.kstars.ekos.capture] - "Capturing 1.000-second  image..."
[2022-03-05T22:04:07.852 CET DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MM Pro : "[DEBUG] StartExposure->setexp : 1.000s "
[2022-03-05T22:04:08.532 CET DEBG ][           org.kde.kstars.indi] - INDI Server:  "2022-03-05T21:04:08: Driver indi_asi_wheel: Unknown transfer code: #1 LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED"
[2022-03-05T22:04:08.532 CET DEBG ][           org.kde.kstars.indi] - INDI Server:  ""
[2022-03-05T22:04:09.453 CET DEBG ][           org.kde.kstars.indi] - INDI Server:  "2022-03-05T21:04:09: Driver indi_asi_wheel: Unknown transfer code: #1 LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED"
[2022-03-05T22:04:09.454 CET DEBG ][           org.kde.kstars.indi] - INDI Server:  ""
[2022-03-05T22:04:10.370 CET DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MM Pro : "[DEBUG] Uploading file. Ext: fits, Size: 93559680, sendImage? Yes, saveImage? No "
[2022-03-05T22:04:10.863 CET DEBG ][           org.kde.kstars.indi] - INDI Server:  "2022-03-05T21:04:10: Driver indi_asi_wheel: Unknown transfer code: #1 LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED"
[2022-03-05T22:04:10.863 CET DEBG ][           org.kde.kstars.indi] - INDI Server:  ""
[2022-03-05T22:04:11.683 CET DEBG ][           org.kde.kstars.indi] - INDI Server:  "2022-03-05T21:04:11: Driver indi_asi_wheel: Unknown transfer code: #1 LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED"
[2022-03-05T22:04:11.684 CET DEBG ][           org.kde.kstars.indi] - INDI Server:  ""
[2022-03-05T22:04:11.684 CET DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MM Pro : "[DEBUG] BLOB transfer took 1.01427 seconds "
[2022-03-05T22:04:11.685 CET DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MM Pro : "[DEBUG] Upload complete "
[2022-03-05T22:04:11.697 CET WARN ][                       default] - QObject::startTimer: Timers can only be used with threads started with QThread
[2022-03-05T22:04:11.701 CET WARN ][                       default] - QtDBus: cannot relay signals from parent Phonon::AbstractAudioOutput(0x4ef81a8 "") unless they are emitted in the object's thread QThread(0x1dc0270 ""). Current thread is QThread(0xa814ab10 "").
[2022-03-05T22:04:11.702 CET WARN ][                       default] - QtDBus: cannot relay signals from parent QObject(0x4ef81a8 "") unless they are emitted in the object's thread QThread(0x1dc0270 ""). Current thread is QThread(0xa814ab10 "").


I tried to launch with valgrind to see more but it was desperately slow, the main screen didn't show up even after several minutes.
Attached is the video showing memory increase (using htop) and KStar crash. Please let me know if you need something else.

Many thanks,
Radim 
2 years 1 month ago #81129
Attachments:

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

  • Posts: 114
  • Thank you received: 5
I had the same issue with mine. Same build, different camera (DSLR). I first noticed an error dialog appear "Debayer Error". In the long run, I disabled my FITS viewer and it has been working well. I still need more testing, but there appears to be a commonality.
2 years 1 month ago #81180

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

  • Posts: 1187
  • Thank you received: 370
This problem comes from the fact that a process in 32bit Linux cannot allocate more than roughly 3GB. Switching to 64bit versions solves the problem.

Turning off the FITS viewer reduces the memory consumption, since each module or window showing a captured frame (FITS viewer, summary page, focus, align) all have their own image buffer.

HTH
Wolfgang
2 years 1 month ago #81207

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

  • Posts: 114
  • Thank you received: 5
Yes, it appears correct, I have disabled all use of the FITS Viewer and my crash rate has dropped significantly.
I am still concerned over the internal FITS Viewer as that also may be causing some crash issues. Overall most of my sessions now are without error and now only occur when carrying out focus and alignment functions.

The 64-bit operating system for Raspberry Pi has not been out for long, so the FITS Viewer appears to have been designed incorrectly for 32-bit systems. 

I will when time change to a 64-bit system once I figure out how to do it.
2 years 1 month ago #81357

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

  • Posts: 2877
  • Thank you received: 812
Also note that Jasem and I just did a bunch of work that might reduce memory consumption in Star Extraction and related tasks in 3.5.8, which might make a difference.  It won't fix the issue what Wolfgang mentioned, but it might make a difference.
2 years 1 month ago #81411

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

Time to create page: 0.491 seconds