×

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

Bi-monthly release with minor bug fixes and improvements

Ekos crash in stellarsolver

  • Posts: 300
  • Thank you received: 57
Here's a crash last night in KStars 3.5.9 beta ubuntu 20.04.3 nightly spa

Thread 14 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff9ffff700 (LWP 6066)]
tcache_get (tc_idx=<optimized out>) at malloc.c:2937
#0 tcache_get (tc_idx=<optimized out>) at malloc.c:2937
#1 __GI___libc_malloc (bytes=60) at malloc.c:3051
#2 0x00007ffff6a5c873 in SEP::addobjdeep(int, SEP::objliststruct*, SEP::objliststruct*, int) () from /lib/x86_64-linux-gnu/libstellarsolver.so.2
#3 0x00007ffff6a581da in SEP::Deblend::deblend(SEP::objliststruct*, int, SEP::objliststruct*, int, double, int, SEP::Lutz*) () from /lib/x86_64-linux-gnu/libstellarsolver.so.2
#4 0x00007ffff6a58a36 in SEP::Extract::sortit(SEP::infostruct*, SEP::objliststruct*, int, SEP::objliststruct*, int, double, double) () from /lib/x86_64-linux-gnu/libstellarsolver.so.2
#5 0x00007ffff6a5af63 in SEP::Extract::sep_extract(SEP::sep_image*, float, int, int, float*, int, int, int, int, double, int, double, SEP::sep_catalog**) () from /lib/x86_64-linux-gnu/libstellarsolver.so.2
#6 0x00007ffff6a18508 in InternalExtractorSolver::extractPartition(InternalExtractorSolver::ImageParams const&) () from /lib/x86_64-linux-gnu/libstellarsolver.so.2
#7 0x00007ffff6a216e9 in non-virtual thunk to QtConcurrent::RunFunctionTask<QList<FITSImage::Star> >::run() () from /lib/x86_64-linux-gnu/libstellarsolver.so.2
#8 0x00007ffff518cf82 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x00007ffff51899d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007ffff6b09609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#11 0x00007ffff4a54163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
2 years 5 days ago #81654

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

Repeatable? go the image that caused it?
2 years 4 days ago #81677

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

  • Posts: 300
  • Thank you received: 57
Thank you for your help!

It's repeatable in that Ekos eventually crashes pretty much every imaging session. Not repeatable in that it runs just fine for hours and then crashes at apparently random times when I'm asleep.

I will continue to try to document the crashes. Perhaps this is the wrong place to post the crash reports?

Should I just provide a link to the last successful saved image as the one that "caused it?"
2 years 4 days ago #81678

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

That image *might* be useful, not sure. Doesn't hurt to test if it can lead to a crash.
2 years 4 days ago #81679

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

Time to create page: 0.180 seconds