×

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

Bi-monthly release with minor bug fixes and improvements

[SOLVED] Kstars keeps crashing

  • Posts: 116
  • Thank you received: 2

Replied by Joshua R on topic Kstars keeps crashing

Is it also possible to connect the devices one by one thru a script manually?
3 years 7 months ago #58923
The topic has been locked.
  • Posts: 1009
  • Thank you received: 133
Should be possible via indi_setprop, e.g.,
indi_setprop "CCD Simulator.CONNECTION.CONNECT=On"

Use option "-h <IP>" if it's on another computer, and in doubt indi_getprop to see available settings...
3 years 7 months ago #58927
The topic has been locked.
  • Posts: 116
  • Thank you received: 2

Replied by Joshua R on topic Kstars keeps crashing

Thanx a lot
3 years 7 months ago #58934
The topic has been locked.
  • Posts: 10
  • Thank you received: 0
Still having issues with the latest build, with the patch. The application is getting further. I can setup a device now, but when I go back in and try to load a configuration, it crashes again.
 
Starting program: /home/myuser/sand-box/kstars/kstars/kstars
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdc106700 (LWP 24088)]
[New Thread 0x7fffd1fb6700 (LWP 24090)]
[New Thread 0x7fffd17b5700 (LWP 24091)]
[New Thread 0x7fffcbfff700 (LWP 24092)]
[New Thread 0x7fffbffff700 (LWP 24094)]
[New Thread 0x7fffb77fe700 (LWP 24095)]
[New Thread 0x7fffbf7fe700 (LWP 24096)]
[New Thread 0x7fffbe5ed700 (LWP 24101)]
[New Thread 0x7fffbcb9a700 (LWP 24102)]
[New Thread 0x7fffb7fff700 (LWP 24103)]
[New Thread 0x7fffb6ffd700 (LWP 24104)]
[New Thread 0x7fff9ffff700 (LWP 24105)]
[New Thread 0x7fffb48f9700 (LWP 24106)]
[New Thread 0x7fff9f7fe700 (LWP 24107)]
[New Thread 0x7fff9effd700 (LWP 24108)]
[New Thread 0x7fff9e7fc700 (LWP 24109)]
[New Thread 0x7fff9dffb700 (LWP 24110)]
[New Thread 0x7fff9d5bf700 (LWP 24111)]
[Thread 0x7fff9d5bf700 (LWP 24111) exited]
[Thread 0x7fffbcb9a700 (LWP 24102) exited]
[New Thread 0x7fffbcb9a700 (LWP 24143)]
[New Thread 0x7fff9d5bf700 (LWP 24162)]
 
Thread 1 "kstars" received signal SIGSEGV, Segmentation fault.
0x00005555562d8d54 in INDI::Property::getState() const ()
(gdb) bt
#0  0x00005555562d8d54 in INDI::Property::getState() const ()
#1  0x00005555559d5514 in INDI_P::updateStateLED() (this=0x55555b090ac0) at /home/myuser/sand-box/kstars/kstars/indi/indiproperty.cpp:64
#2  0x00005555559d573a in INDI_P::initGUI() (this=0x55555b090ac0) at /home/myuser/sand-box/kstars/kstars/indi/indiproperty.cpp:101
#3  0x00005555559d52d1 in INDI_P::INDI_P(INDI_G*, INDI::Property*) (this=0x55555b090ac0, ipg=0x55555a14dc10, prop=0x7fffa002ae30)
    at /home/myuser/sand-box/kstars/kstars/indi/indiproperty.cpp:52
#4  0x00005555559d3805 in INDI_G::addProperty(INDI::Property*) (this=0x55555a14dc10, prop=0x7fffa002ae30) at /home/myuser/sand-box/kstars/kstars/indi/indigroup.cpp:74
#5  0x00005555559cfe71 in INDI_D::buildProperty(INDI::Property*) (this=0x55555a66cd60, prop=0x7fffa002ae30) at /home/myuser/sand-box/kstars/kstars/indi/indidevice.cpp:97
#6  0x00005555559cc535 in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<INDI::Property*>, void, bool (INDI_D::*)(INDI::Property*)>::call(bool (INDI_D::*)(INDI::Property*), INDI_D*, void**) (f=(bool (INDI_D::*)(INDI_D * const, INDI::Property *)) 0x5555559cfcfc <INDI_D::buildProperty(INDI::Property*)>, o=0x55555a66cd60, arg=0x7fffa002b9b0)
    at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:136
#7  0x00005555559cc035 in QtPrivate::FunctionPointer<bool (INDI_D::*)(INDI::Property*)>::call<QtPrivate::List<INDI::Property*>, void>(bool (INDI_D::*)(INDI::Property*), INDI_D*, void**) (f---Type <return> to continue, or q <return> to quit---
=(bool (INDI_D::*)(INDI_D * const, INDI::Property *)) 0x5555559cfcfc <INDI_D::buildProperty(INDI::Property*)>, o=0x55555a66cd60, arg=0x7fffa002b9b0)
    at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:169
#8  0x00005555559cb603 in QtPrivate::QSlotObject<bool (INDI_D::*)(INDI::Property*), QtPrivate::List<INDI::Property*>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x55555a663ec0, r=0x55555a66cd60, a=0x7fffa002b9b0, ret=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h:120
#9  0x00007ffff23ed0c2 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007ffff388175b in QWidget::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007ffff384283c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007ffff384a104 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007ffff23bd8d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007ffff23c004d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007ffff2417263 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007fffed34c417 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007fffed34c650 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fffed34c6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ffff241688f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007ffff23bb90a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007ffff23c49b4 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00005555556338e8 in main(int, char**) (argc=1, argv=0x7fffffffdd98) at /home/myuser/sand-box/kstars/kstars/main.cpp:348
 
3 years 7 months ago #58992
The topic has been locked.
  • Posts: 1009
  • Thank you received: 133
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
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
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.
Time to create page: 1.229 seconds