×

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

Bi-monthly release with minor bug fixes and improvements

KStars disappears / crashed?

  • Posts: 1
  • Thank you received: 0
Was this software released without being tested?

I'm on the verge of going back to SGP.
3 years 6 months ago #60271

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

  • Posts: 643
  • Thank you received: 62
Hi!

well, all software have issues, for a great variety of reasons. Do you have any particular that would cause you to abandon this project?

My crashes were identified and solved by Jasem right now. A level of testing and fixing that beats anything I ever experienced in commercial software...

So as for the thread topic: at least one cause for crashes seems to be solved, as we speak.

Magnus
3 years 6 months ago #60295

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

  • Posts: 62
  • Thank you received: 1
Hi,

I have the same experience - Kstars suddenly crashes/disappears.
Last time it happened it was right after a meridian flip, in iteration #2 of the solver (please see attached log).
It seems it happened right after the image taken by the solver was downloaded.

I also often get this behaviour after I have captured my flat frames and start taking the first light frame.
To reduce the risk of this to happen, I now have a routine to always restart the Stellarmate between the flats and the lights.
Not very convenient, but I rather do this than having a crash during the lights session...
So it seems to have something to do with the image capture in my case.

Any ideas/advice on what to do?

Cheers, Åke

File Attachment:

File Name: log_23-24-....txt.zip
File Size:110 KB
3 years 6 months ago #60326
Attachments:

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

  • Posts: 643
  • Thank you received: 62
Hi!

I have no clue to what happened there, but as I understand it, you did not run Kstars from the Ekos Debugger?

I think that is a very good idea to get data on the crashes. Logging data is in the Debugger window, and you choose a directory to save it in as well (do that before you start Kstars with it).

Magnus
3 years 6 months ago #60334

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

  • Posts: 62
  • Thank you received: 1
Hi Magnus,

Thanks for responding so quickly.
Not sure what you mean by "run Kstars from the Ekos Debugger".
I did enable debug logging when starting Ekos, but that is after I started Kstars. I don't know how to start Ekos in any other way, please advice me. Currently, I start Ekos from the Kstars menu: "Toggle Ekos".

Also, not sure if I should enable all logging (since it says "Only enable the necessary logs to help in diagnosing specific problems").
I think what I enabled was:
- Ekos: INDI,Capture,Alignment & Mount
- Drivers: Mount & CCD

// Åke
3 years 6 months ago #60338

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

ekosdebugger is tool that you use to launch KStars so that in case it crashes, it can generate useful logs for developers. You can install it on Linux:
sudo apt-get -y install ekos-debugger
3 years 6 months ago #60340

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

  • Posts: 319
  • Thank you received: 25
GM everyone,

I'm sharing my experience and what I believe went wrong (and fixed) for me. I was using a USB extension cable to increase the length of the RPi power cord. When I tested this on my RPi test unit, the insufficient power warning was always popping up. I suspected that I'm using the old power supply for RPi 3, but it was the extension cable. The volt was correct but the Amp dropped below 3A. I removed it yesterday and I was able to get a continuous session for more than 6 hours without interruption. I used the ekos debugger, but there were no interruptions to report. There were other problems, but it was my mistake in ekos configuration.

3 years 6 months ago #60341
Attachments:

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

  • Posts: 62
  • Thank you received: 1

Thank for the reply.
So I installed the debugger, but how do I launch KStars with it? Sorry for my ignorance.

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

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

If you launch it, make sure you're in the KStars tab, then click the Play button.
3 years 6 months ago #60345

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

  • Posts: 62
  • Thank you received: 1
OK, but how do I start the debugger? I can't find it anywhere...
EDIT: I see it now, I have to start it from the command prompt!
Last edit: 3 years 6 months ago by Åke Liljenberg.
3 years 6 months ago #60346

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

  • 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.

Time to create page: 0.461 seconds