In at least the last two commits with git, I noticed I get about 2-3 hours into an imaging run and kstars crashes. The indiserver continues running. Logfiles reveal nothing, they just stop. Backtrace from gdb: Thread 1 "kstars" received signal SIGABRT, Aborted. 0x00007ffff17f7428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007ffff17f7428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #1 0x00007ffff17f902a in __GI_abort () at abort.c:89 #2 0x00007ffff213a84d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #3 0x00007ffff21386b6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x00007ffff2138701 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x00007ffff2138919 in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #6 0x00007ffff3cba072 in qBadAlloc() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x00007ffff3d60305 in QString::reallocData(unsigned int, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007ffff3d60b72 in QString::append(QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x000055555584daa0 in ServerManager::processStandardError (this=0x555558dbbb60) at /home/schwim/src/kstars/kstars/indi/servermanager.cpp:292 #10 0x0000555555807f66 in ServerManager::qt_static_metacall (_o=0x555558dbbb60, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0x7fffffffd550) at /home/schwim/src/build/kstars/kstars/moc_servermanager.cpp:107 #11 0x00007ffff3ee0d2a in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x00007ffff3de7d7c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x00007ffff3de8568 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00007ffff3ee0d2a in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x00007ffff3f6024e in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x00007ffff3eed1cb in QSocketNotifier::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007ffff4c2005c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x00007ffff4c25516 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x00007ffff3eb238b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x00007ffff3f08c95 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ---Type <return> to continue, or q <return> to quit--- #21 0x00007fffee0fd197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x00007fffee0fd3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x00007fffee0fd49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x00007ffff3f087cf in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x00007ffff3eafb4a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x00007ffff3eb7bec in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x00005555556204fb in main (argc=1, argv=0x7fffffffdf68) at /home/schwim/src/kstars/kstars/main.cpp:322
What were the drivers were you running? Do you know if any of these drivers print to stderr? Because one *theory* about what could be causing this is that the buffer is running out of memory. I'm working on a different design now that doesn't store the log from the server in memory but to a file.
Git commit fad13ccae4a2ef19bad614689a47fc478a6586ee by Jasem Mutlaq. Committed on 26/02/2018 at 10:54. Pushed by mutlaqja into branch 'master'. FIXED-IN:2.9.3 Possible fix for crash due to memory issue of server buffer. Using QTemporaryFile instead of QString to store the server log information. M +20 -6 kstars/indi/servermanager.cpp M +3 -2 kstars/indi/servermanager.h https://commits.kde.org/kstars/fad13ccae4a2ef19bad614689a47fc478a6586ee
I was using the following drivers: indi_paramount_telescope indi_fli_ccd indi_fli_filter indi_sx_ccd indi_gpsd indi_gemini_focus I'll try the updates.