×

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

Bi-monthly release with minor bug fixes and improvements

Read More...

[SOLVED] Kstars keeps crashing

  • Posts: 1009
  • Thank you received: 133

Replied by Peter Sütterlin on topic Kstars keeps crashing

I had just installed latest KStars and INDI. No crashes here, neither with manually connecting devices, nor with autoconnect. (Just ASI cam won't connect - see separate post)
System see signature...
Or does it depend on specific devices? That was 2 ZWo cameras (1600/290), EFW and EAF, plus the telescope simulator...
3 years 7 months ago #59000
The topic has been locked.
  • Posts: 10
  • Thank you received: 0

Replied by William Curtis on topic Kstars keeps crashing

Latest PPA or latest Github?
3 years 7 months ago #59001
The topic has been locked.
  • Posts: 294
  • Thank you received: 54

Replied by Gilles Gagnon on topic Kstars keeps crashing

I have a system being investigated on for the crash issue (was either PPA or github with patch), and I also installed from scratch (Ubuntu Mate 20.04 LTS and KStars 3.4.3 & friends, from PPA) on an identical system (ODroid C4) that does not seem to have the issue. I haven't tested it with hardware yet though.

More to come I hope.
3 years 7 months ago #59002
The topic has been locked.
  • Posts: 148
  • Thank you received: 19

Replied by JAMIE FLINN on topic Kstars keeps crashing

Latest update on buster side (stellarmate PI4 8 gig) still crashes:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[New Thread 0xafb86090 (LWP 4028)]
[New Thread 0xaa2d7090 (LWP 4029)]
[New Thread 0xa9360090 (LWP 4030)]
[New Thread 0xa735f090 (LWP 4031)]
[New Thread 0xa51ff090 (LWP 4032)]
[New Thread 0xa23f4090 (LWP 4033)]
[New Thread 0xa17da090 (LWP 4034)]
[New Thread 0xa0dff090 (LWP 4035)]
[New Thread 0xa05fe090 (LWP 4036)]
[New Thread 0x9fdfd090 (LWP 4037)]
[New Thread 0x9f5fc090 (LWP 4038)]
[New Thread 0x9ecb7090 (LWP 4039)]
[New Thread 0x9ccb6090 (LWP 4040)]
[Thread 0x9ccb6090 (LWP 4040) exited]
[Thread 0xa17da090 (LWP 4034) exited]
[Thread 0x9fdfd090 (LWP 4037) exited]
[New Thread 0x9fdfd090 (LWP 4048)]
[New Thread 0xa17da090 (LWP 4071)]
[New Thread 0x9ccb6090 (LWP 4073)]
[New Thread 0x9b2ff090 (LWP 4075)]
Thread 1 "kstars" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0xb3aeb230 in __GI_abort () at abort.c:79
#2 0xb3d458d8 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#3 0xb3d435b0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#4 0xb3d43624 in std::terminate() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#5 0xb3d43990 in __cxa_throw () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#6 0xb3d6c234 in std::__throw_logic_error(char const*) () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#7 0x00a44dc4 in INDI::BaseDevice::messageQueue[abi:cxx11](int) const ()
#8 0x006602b6 in INDI_D::updateMessageLog (this=0xa9944fe8, idv=0xa9922038, messageID=<optimized out>) at ./kstars/indi/indidevice.cpp:293
#9 0xb4b64c68 in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#10 0xb4b68bec in QObject::event(QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#11 0xb54a09c4 in QWidget::event(QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#12 0xb545ddb4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#13 0xb54662a8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
Backtrace stopped: Cannot access memory at address 0x428e10f8
3 years 7 months ago #59003
The topic has been locked.
  • Posts: 108
  • Thank you received: 20

Replied by ouioui01 on topic Kstars keeps crashing

Hello,

Same thing with last git in rpi4 8G, ubuntu 20.04.1

Clear skies
3 years 7 months ago #59004
The topic has been locked.
  • Posts: 10
  • Thank you received: 0

Replied by William Curtis on topic Kstars keeps crashing

Everything works fine for me, until I add hardware, shutdown kstars, and then restart. Once I go to "start" INDI in EKOS/Kstars, it fails.

FYI, I am excited to try out the new features, I hope this can get resolved.
3 years 7 months ago #59005
The topic has been locked.
  • Posts: 148
  • Thank you received: 19

Replied by JAMIE FLINN on topic Kstars keeps crashing

I can reproducer this error SIGABORT now with any combination of devices (no longer juts the ASI camera) - currently I am down to only mount and cam and still crashing...simulators I can run!!!!
3 years 7 months ago #59006
The topic has been locked.
  • Posts: 148
  • Thank you received: 19

Replied by JAMIE FLINN on topic Kstars keeps crashing

And another variant of this same crash - this time controlled - unchecked auto connect and let EKOS come up then connected mount = OK....connected ZWO cam (I expected crashed here) = OK....so now connected QHY cam (whihc has always bee stable) = CRASH

SIGABORT is related to running out of memory from what I know so there seems to be a dynamic memory issue here since simulator can load but have no real load - I notices there is a new analyis icon/tab - could it be that that new feature is grabbing objects and eating the system?....can that utility be disabled by config so I can run a test of that theory?

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[New Thread 0xafb86090 (LWP 1487)]
[New Thread 0xaa2d7090 (LWP 1488)]
[New Thread 0xa9360090 (LWP 1489)]
[New Thread 0xa735f090 (LWP 1490)]
[New Thread 0xa51ff090 (LWP 1491)]
[New Thread 0xa23f4090 (LWP 1492)]
[New Thread 0xa17da090 (LWP 1493)]
[New Thread 0xa0dff090 (LWP 1494)]
[New Thread 0xa05fe090 (LWP 1495)]
[New Thread 0x9fdfd090 (LWP 1496)]
[New Thread 0x9f5fc090 (LWP 1497)]
[New Thread 0x9ecb7090 (LWP 1498)]
[New Thread 0x9ccb6090 (LWP 1499)]
[Thread 0x9ccb6090 (LWP 1499) exited]
[Thread 0xa17da090 (LWP 1493) exited]
[Thread 0x9fdfd090 (LWP 1496) exited]
[Thread 0xa0dff090 (LWP 1494) exited]
[New Thread 0xa0dff090 (LWP 1506)]
[New Thread 0x9fdfd090 (LWP 1508)]
[New Thread 0xa17da090 (LWP 1509)]
[New Thread 0x9ccb6090 (LWP 1513)]
[Thread 0x9fdfd090 (LWP 1508) exited]
[Thread 0xa17da090 (LWP 1509) exited]
[Thread 0xa0dff090 (LWP 1506) exited]
[New Thread 0xa0dff090 (LWP 1529)]
[New Thread 0xa17da090 (LWP 1553)]
[New Thread 0x9fdfd090 (LWP 1556)]
[New Thread 0x9a122090 (LWP 1562)]
Thread 1 "kstars" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0xb3aeb230 in __GI_abort () at abort.c:79
#2 0xb3d458d8 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#3 0xb3d435b0 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#4 0xb3d43624 in std::terminate() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#5 0xb3d43990 in __cxa_throw () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#6 0xb3d6c234 in std::__throw_logic_error(char const*) () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#7 0x00a44dc4 in INDI::BaseDevice::messageQueue[abi:cxx11](int) const ()
#8 0x006602b6 in INDI_D::updateMessageLog (this=0xa2f20150, idv=0xa2f20ed0, messageID=<optimized out>) at ./kstars/indi/indidevice.cpp:293
#9 0xb4b64c68 in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#10 0xb4b68bec in QObject::event(QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#11 0xb54a09c4 in QWidget::event(QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#12 0xb545ddb4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#13 0xb54662a8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
Backtrace stopped: Cannot access memory at address 0x4317c6f8
3 years 7 months ago #59007
The topic has been locked.
  • Posts: 108
  • Thank you received: 20

Replied by ouioui01 on topic Kstars keeps crashing

It seems that Jasem's patch works for me after compiling kstars. no more crashing...
I'm using RPI4 8G with ubuntu 20.04.1 x64

Cheers
Last edit: 3 years 7 months ago by ouioui01.
3 years 7 months ago #59019
The topic has been locked.
  • Posts: 148
  • Thank you received: 19

Replied by JAMIE FLINN on topic Kstars keeps crashing

will this patch be built into nightly?....I am running stellarmate and do not have a dev environment installed
3 years 7 months ago #59020
The topic has been locked.
  • Posts: 10
  • Thank you received: 0

Replied by William Curtis on topic Kstars keeps crashing

I kept on chugging through this issue.
  • Complete uninstall of KStars and INDI, re-installed.
  • Cleaned out the .indi and .local/share/kstars folders
  • Downloaded KStars from Github
  • Recompiled

At this point, application was broken like it was. Then I applied the patch. Still broken, but with new error around the Status LED.

Thinking that the problem was related to threading, I extended the Blocking Queue and Queued Connections to the individual components. This appears to have worked.
 # In the indilistener.cpp
    connect(cm, &ClientManager::newINDIDevice, this, &INDIListener::processDevice, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::newINDIProperty, this, &INDIListener::registerProperty, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::removeINDIDevice, this, &INDIListener::removeDevice, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::removeINDIProperty, this, &INDIListener::removeProperty, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::newINDISwitch, this, &INDIListener::processSwitch, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::newINDIText, this, &INDIListener::processText, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::newINDINumber, this, &INDIListener::processNumber, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::newINDILight, this, &INDIListener::processLight, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::newINDIBLOB, this, &INDIListener::processBLOB, Qt::BlockingQueuedConnection);
 
#in the guimanager.cpp
    connect(cm, &ClientManager::newINDISwitch, gdm, &INDI_D::updateSwitchGUI, Qt::QueuedConnection);
    connect(cm, &ClientManager::newINDIText, gdm, &INDI_D::updateTextGUI, Qt::QueuedConnection);
    connect(cm, &ClientManager::newINDINumber, gdm, &INDI_D::updateNumberGUI, Qt::QueuedConnection);
    connect(cm, &ClientManager::newINDILight, gdm, &INDI_D::updateLightGUI, Qt::QueuedConnection);
    connect(cm, &ClientManager::newINDIBLOB, gdm, &INDI_D::updateBLOBGUI, Qt::QueuedConnection);
    connect(cm, &ClientManager::newINDIMessage, gdm, &INDI_D::updateMessageLog, Qt::QueuedConnection);
 
 
 
3 years 7 months ago #59026
The topic has been locked.

Replied by Jasem Mutlaq on topic Kstars keeps crashing

That would result in a deadlock. I now have a working solution that I'm just testing through all scenarios... just waiting for Gilles to confirm it's working well on his system.
The following user(s) said Thank You: Gilles Gagnon
3 years 7 months ago #59027
The topic has been locked.
Time to create page: 1.388 seconds