Created attachment 112875 [details] crash log I have two ZWO cameras ZWO ASI1600MC-C for imaging and ZWO ASI120MC-S for guiding. In the guiding panel, when I click on Capture or Loop this results in a KStars crash. I reported this bug previously. See attached logs Regards
I just tested on MacOS with a similar setup (2 ZWO cameras) and couldn't get a crash. Also, your attachment does not show any crash. If there is a crash, MacOS generates a report. The attachment is KStars log, not the crash report.
Created attachment 112876 [details] Apple crash report Apple crash report
Thanks for the crash report. It's not really clear from the report what actually caused the crash. I will ask Robert to look into this. Does this happen if you only have one camera connected?
I will test this in one hour in detail, but I think no (see a previous crash report https://bugs.kde.org/show_bug.cgi?id=384171)
Created attachment 112878 [details] 2 crash process 2 crash process
OK, I’m going forward. I’ve done two types of tests : First test : - 2 cameras are connected (ZWO ASI1600MC-C for imaging and ZWO ASI120MC-S for guiding) - Start INDI - Focus Panel : Select CCD = ASI120, Capture = crash (Apple report Process 2 cams) - I get also a crash if I had disconnected logically the camera ZWO ASI1600MC-C after Start INDI Second test : - 1 camera is connected (ZWO ASI120MC-S) (ZWO ASI1600MC-C is physically disconnected) - Start INDI - Focus Panel : Select CCD = ASI120 (no choice), Capture = crash (Apple report Process 1 cams) Hence it seems that the camera ZWO ASI120MC-S has a problem. Is this only mine ?
Created attachment 112879 [details] Process only ZWO ASI120MC-S
And another step : only the camera ZWO ASI120MC-S was connected directly to KStars (all other devices were disconnected physically). I still get a crash (attached file : Process only ZWO ASI120MC-S)
Can you connect without MaxDomeII? Just the cameras.
(In reply to Jasem Mutlaq from comment #9) > Can you connect without MaxDomeII? Just the cameras. Yes I can connect the camera to KStars (no other devices being physically connected). And then if I follow the procedure : - Start INDI - Focus Panel : Select CCD = ASI120, Capture KStars crashes, maybe one out of two times. Sometimes it works well.
Created attachment 112887 [details] Bin 2x2
(I have difficulty with text + attachment) I realized that the crashes occur much more often if bin 2x2 than bin 1x1
Summary : - Only the camera ZWO ASI120MC-S is connected to KStars with a USB 3.0 cable. - No other app is running. - Start INDI - Focus Panel : Select CCD = ASI120-S, Capture = crash - Guider Panel : Select CCD = ASI120-S, Capture = crash if Bin = 2x2 and NO SUBFRAME - Guider Panel : Select CCD = ASI120-S, Capture = NO CRASH if Bin = 2x2 and SUBFRAME This happens systematically if Bin = 2x2 KStars crashes also in the Guider Panel for a Capture if Bin = 2x2 and NO SUBFRAME. This happens only on my MacBook Pro , never on my iMac Replacing completely KStars (app + Library files & folders) on the MacBook Pro by the ones from the iMac doesn’t help. Restarting the MacBook Pro with the extensions OFF doesn’t help. Could it be that the crash is caused by a flux of data which is too big for the USB 3.0 ports of the MacBook Pro (mid 2014) ?
No crash on running the same MacBook Pro on Windows 10 located on an external SSD. I got NO crash if Bin = 2x2 with or without subframe !
Created attachment 113391 [details] Missing library glibc >= 2.1
Apparently my comments are lost ! Here are my comments again on the missing library : First I created a Ekos profile containing only my two ZWO cameras ZWO ASI1600MC-C for imaging and ZWO ASI120MC-S for guiding. Then I limited the debug logs to the necessary Ekos / INDI + Guider and Drivers / CCD After the crash the log reports that there is a missing glibc >= 2.1 Is this a library ? Apparently KStars might try to do a zero divide and crashes. Thank you
I just found where are stored the Console crash reports . I attach a zip folder "Console crash reports.zip" containing two crash reports for those who know to read them : 1- kstars_2018-06-17-160611_MacBookProJCJ 2- indiserver_2018-06-17-170613_MacBookProJCJ.crash
Created attachment 113392 [details] Console crash reports.zip
I resolved this bug after reinstalling my system. I arrived to this "solution" after having observed that : - the bug didn't occur on a new system - it didn't occur either with other users. Thus it seems that conflict occurred between the KStars ZWO camera driver and some unknown additional installation.