Kstars crashing

[Wolfgang Reissenberger]

Last night everything ran fine. I disabled „Load all Indexes into Memory“. So maybe the problem lies somewhere there…

Wolfgang

> Am 31.03.2021 um 10:11 schrieb Jasem Mutlaq <mutlaqja at ikarustech.com>:
> 
> This is my profile
> 
> <Screenshot_20210331_111056.png>
> --
> Best Regards,
> Jasem Mutlaq
> 
> 
> 
> On Wed, Mar 31, 2021 at 11:10 AM Jasem Mutlaq <mutlaqja at ikarustech.com <mailto:mutlaqja at ikarustech.com>> wrote:
> Hi Wolfgang,
> 
> I tried to replicate the crash but couldn't. Connected to remote mount and and focuser (EQMod  + NightCrawler) while connected to local camera at the same time. No crash.
> --
> Best Regards,
> Jasem Mutlaq
> 
> 
> 
> On Tue, Mar 30, 2021 at 3:59 PM Wolfgang Reissenberger <sterne-jaeger at openfuture.de <mailto:sterne-jaeger at openfuture.de>> wrote:
> Hi Jasem,
> yes, it’s the latest one. Maybe that my setup is slightly special, since I have my mount and the focuser running on a remote INDI server, while the cameras for imaging and guiding are attached to the local INDI server where Kstars is running.
> 
> I‘ve seen Kstars crashing at exactly the same position where the status light of the mount is set. But there is nothing special there, no clue why a segmentation fault occurs here.
> Any ideas about this?
> 
> Wolfgang 
> 
>> Am 30.03.2021 um 10:56 schrieb Jasem Mutlaq <mutlaqja at ikarustech.com <mailto:mutlaqja at ikarustech.com>>:
>> 
>> Hello Wolfgang,
>> 
>> Did you update libindi to the latest?
>> 
>> --
>> Best Regards,
>> Jasem Mutlaq
>> 
>> 
>> 
>> On Tue, Mar 30, 2021 at 10:49 AM Wolfgang Reissenberger <sterne-jaeger at openfuture.de <mailto:sterne-jaeger at openfuture.de>> wrote:
>> Dear all,
>> This morning I had a kstars crash that appeared after kstars ran since yesterday evening. The core dump shows the following stack trace:
>> 
>> ——————————————————————————————————————————————————————————————————————
>> Core was generated by `./kstars/kstars'.
>> Program terminated with signal SIGSEGV, Segmentation fault.
>> #0  0xb48384e0 in QColor::operator==(QColor const&) const ()
>>    from /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
>> [Current thread is 1 (Thread 0xafcc1010 (LWP 9779))]
>> (gdb) bt
>> #0  0xb48384e0 in QColor::operator==(QColor const&) const ()
>>     at /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
>> #1  0xb5933244 in KLed::setColor(QColor const&) ()
>>     at /usr/lib/arm-linux-gnueabihf/libKF5WidgetsAddons.so.5
>> #2  0x008d6248 in INDI_P::updateStateLED() (this=0x2495e60)
>>     at /home/wolfgang/sterne-jaeger/git/kstars/kstars/indi/indiproperty.cpp:67
>> #3  0x008cf7b8 in INDI_D::updateNumberGUI(_INumberVectorProperty*)
>>     (this=0x520c6e0, nvp=0xa8b948a8)
>>     at /home/wolfgang/sterne-jaeger/git/kstars/kstars/indi/indidevice.cpp:242
>> #4  0x008cb250 in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<_INumberVectorProperty*>, void, bool (INDI_D::*)(_INumberVectorProperty*)>::call(bool (INDI_D::*)(_INumberVectorProperty*), INDI_D*, void**) (f=
>>     (bool (INDI_D::*)(INDI_D * const, _INumberVectorProperty *)) 0x8cf67c <INDI_D::updateNumberGUI(_INumberVectorProperty*)>, o=0x520c6e0, arg=0xa8b2a5b0)
>>     at /usr/include/arm-linux-gnueabihf/qt5/QtCore/qobjectdefs_impl.h:134
>> #5  0x008caa64 in QtPrivate::FunctionPointer<bool (INDI_D::*)(_INumberVectorProperty*)>::call<QtPrivate::List<_INumberVectorProperty*>, void>(bool (INDI_D::*)(_INumberVectorProperty*), INDI_D*, void**) (f=
>>     (bool (INDI_D::*)(INDI_D * const, _INumberVectorProperty *)) 0x8cf67c <INDI_D::updateNumberGUI(_INumberVectorProperty*)>, o=0x520c6e0, arg=0xa8b2a5b0)
>>     at /usr/include/arm-linux-gnueabihf/qt5/QtCore/qobjectdefs_impl.h:167
>> #6  0x008ca014 in QtPrivate::QSlotObject<bool (INDI_D::*)(_INumberVectorProperty*), QtPrivate::List<_INumberVectorProperty*>, void>::impl(int, QtPrivate::QSlotO
>> ——————————————————————————————————————————————————————————————————————
>> 
>> In the kstars log, the last action was an alignment that just started.
>> 
>> On the console, I found the following messages repeatedly:
>> system: Cannot allocate memory
>> /home/wolfgang/sterne-jaeger/git/stellarsolver/stellarsolver/astrometry/util/fitsbin.c:541:read_chunk: Couldn't mmap file "/home/wolfgang/.local/share/kstars/astrometry/index-4107.fits“
>> 
>> Any ideas?
>> 
>> Wolfgang
>> 
>> —
>> Wolfgang Reissenberger
>> 
>> www.sterne-jaeger.de <http://www.sterne-jaeger.de/>
>> TSA-120 + FSQ-85 | Avalon Linear + M-zero | Moravian G2-8300 + ASI 1600mm pro
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kstars-devel/attachments/20210331/5c1d6b0f/attachment.htm>