×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

KStars disappears / crashed?

  • Posts: 62
  • Thank you received: 1
It seems to crash randomly. I'm playing around a bit to try to provoke it and this time it crashed when stopping Ekos by clicking the "Stop"

File Attachment:

File Name: log_18-28-10.txt.zip
File Size:154 KB
button in the "Setup" tab of Ekos.
The debug log is attached. It doesn't show much I believe, but the following showed up in the EkosDebugger window:
Thread 451 "kstars" received signal SIG32, Real-time event 32.
[Thread 0x8a583090 (LWP 8019) exited]
[Thread 0x80a9f090 (LWP 8018) exited]
[Thread 0x98bb3090 (LWP 6350) exited]
[Thread 0x983b2090 (LWP 6351) exited]
[Thread 0x97bb1090 (LWP 6352) exited]
[Thread 0x973b0090 (LWP 6353) exited]
Thread 1 "kstars" received signal SIGSEGV, Segmentation fault.
0xb6fbc1dc in strlen () from /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so
#0  0xb6fbc1dc in strlen () from /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so
#1  0x004a6650 in QString::QString (this=0xbeffe908, ch=0xe0 <error: Cannot access memory at address 0xe0>) at /usr/include/arm-linux-gnueabihf/qt5/QtCore/qstring.h:693
#2  0x0067ae56 in ISD::CCD::loadImageInView (this=this@entry=0x4723260, bp=bp@entry=0xa7f1f520, targetChip=targetChip@entry=0x474c020, data=data@entry=0x44340b8) at ./kstars/indi/indiccd.cpp:1809
#3  0x0067c872 in ISD::CCD::displayFits (this=this@entry=0x4723260, targetChip=targetChip@entry=0x474c020, filename=..., bp=bp@entry=0xa7f1f520, blob_fits_data=blob_fits_data@entry=0x44340b8) at ./kstars/indi/indiccd.cpp:1800
#4  0x0067f712 in ISD::CCD::processBLOB (this=0x4723260, bp=0xa7f1f520) at ./kstars/indi/indiccd.cpp:1725
#5  0xb4b69380 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#6  0x0060bd1a in ClientManager::newINDIBLOB (this=<optimized out>, _t1=<optimized out>) at ./obj-arm-linux-gnueabihf/kstars/KStarsLib_autogen/FRI4DANIHA/moc_clientmanager.cpp:364
#7  0xb4b65c68 in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#8  0xb4b69bec in QObject::event(QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#9  0xb545edb4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#10 0xb54672a8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#11 0x0370c638 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".

Hope this helps debugging.
Please advice me if any more tests and/or logs are required.

Cheers,
// Åke
3 years 6 months ago #60370
Attachments:

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

  • Posts: 62
  • Thank you received: 1
Don't know if this helps, but it doesn't seem all random.
I've got a feeling that the crashes normally happens where there is image capture activity of some kind, either when changing between flat frames to light frames or when there is an interruption by e.g. a meridian flip and the solver needs to capture some images.
Also in the output I provided in the previous post there are statements like "ISD::CCD::loadImageInView".
Could it be something in this area?

BR,
// Åke
3 years 6 months ago #60388

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

  • Posts: 319
  • Thank you received: 25
It is not a power issue. Something else is going on. KStars crashed yesterday after shooting for about 1.5 hours.

PFA complete log from the ekos debugger

File Attachment:

File Name: ekoslogs.zip
File Size:9,809 KB



Edit: Please we need this to be fixed as today's morning I found the scope continues to track (while ekos is not controlling) and the back of the camera was pushed to the tripod. I think INDI was working anyway in spite of KStars presence.
Last edit: 3 years 6 months ago by Mohamed.
3 years 6 months ago #60422
Attachments:

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

I believe this specific crash was fixed in 3.5.0 Beta. Please try that.
3 years 6 months ago #60423

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

  • Posts: 62
  • Thank you received: 1
Thanks a lot Jasem!
Where do I download 3.5.0 Beta? Is it part of the "StellarMateOS_1.5.4.img.xz" file?

I have provoked a new crash log just a moment ago - does this mean you don't need it then?

Cheers,
// Åke
3 years 6 months ago #60425

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

  • Posts: 62
  • Thank you received: 1
Hello Jasem,

I just discovered I'm using 3.5.0 Beta already.

I just provoked another crash, please see the attached logs.
The way I provoked it was to loop the image capture in the guide module (to kind of simulate the autoguiding, using a ZWO ASI 120 MM-S camera) and at the same time capturing a series of 300 sec images (in the CCD module) with the telescope camera, a ZWO ASI294MC pro.
It suddenly crashed leaving me with just an empty desktop screen.

Best regards,
// Åke
Last edit: 3 years 6 months ago by Åke Liljenberg.
3 years 6 months ago #60427
Attachments:

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

  • Posts: 62
  • Thank you received: 1
Hi again,
Is there any chance this bug will be looked into in a near future, or is there any other way I can temporarily avoid this crash?
E.g. is there a way I can disable the FITS viewer (since it seems it's in that area the bug is)?
Just so I can avoid crashes in the precious night sessions :-)

Thanks for your support.

// Åke
3 years 6 months ago #60459

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

In the log, I see the crash when it debayers 16 bit image, but I can't replicate this here with all the cameras I have (Toupcam, Altair..etc) on both desktop and StellarMate without crash. So this could be related to how much RAM maybe you have available? what does free -m show?
3 years 6 months ago #60466

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

  • Posts: 62
  • Thank you received: 1
Thanks for your reply Jasem, very good support!

Right now when I'm in a capturing sequence it says:

total used free shared buff/cache available
Mem: 3650 1502 163 155 1984 1859
Swap: 2837 4 2833

EDIT: By the way, it's a Rapberry PI 4 model B with 4 GB

BR,
// Åke
Last edit: 3 years 6 months ago by Åke Liljenberg.
3 years 6 months ago #60469

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

yeah this is more than enough. I need to dig into this deeper since I cannot reproduce it, so please install teamviewer and contact This email address is being protected from spambots. You need JavaScript enabled to view it. to arrange for a session.
The following user(s) said Thank You: Åke Liljenberg
3 years 6 months ago #60470

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

  • Posts: 319
  • Thank you received: 25
Hi Jassem,

Any update about my Crash log? is it the same issue?
3 years 6 months ago #60479

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


This is most likely fixed in the nightly.
3 years 6 months ago #60482

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

Time to create page: 0.422 seconds