×

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

Bi-monthly release with minor bug fixes and improvements

Using Sony a7C II (ILCE-7CM2) crashes indi_gphoto_ccd

  • Posts: 1
  • Thank you received: 1
Hello,

I have started trying to get a Sony a7C II to work with Ekos/INDI and I have been having some troubles. After about 1 or 2 successful exposures, a pop up stating "INDI Driver GPhoto2 CCD has crashed. Restart it?" appears (often after the camera has started an exposure, it appears). I am often then notified by a log message in Ekos stating "Exposure timeout. Restarting exposure..." with the camera seemingly now not starting an exposure despite Ekos stating it is capturing. The camera is in BULB mode and all of my exposures for testing have been under 30 seconds. Adding a delay after the exposure/download does not seem to help. I believe I am using high quality cables and the camera has a full battery. A simple reproduction happens during this setup (and log is attached):



At this point, it may eventually recover, but KStars will eventually crash after this or future restarts. Looking in the log, it does appear to have started the next exposure with no additional error:
INFO	111.051246 sec	: Starting 15 seconds exposure.
DEBUG	111.051282 sec	: Starting exposure (exptime: 15 secs, mirror lock: 0, force bulb: true, exposure index: 669058672)
DEBUG	111.051293 sec	: Mutex locked
DEBUG	111.051304 sec	: Setting radio/menu widget imagequality: 0 (RAW)
DEBUG	111.051412 sec	: Setting new configuration OK.
DEBUG	111.051423 sec	: Finding optimal exposure setting for 15 seconds in shutterspeed (count=62)...
DEBUG	111.051432 sec	: Closest match: 15 seconds Index: 3
DEBUG	111.051441 sec	: Setting radio/menu widget shutterspeed: 3 (15)
DEBUG	111.051527 sec	: Setting new configuration OK.
DEBUG	111.051537 sec	: Using predefined exposure time: 15 seconds
DEBUG	111.051548 sec	: Exposure started.

Running in gdb with the GPhoto CCD driver compiled with the debug options noted in the support request guide and attaching to the indiserver "Exposure timeout. Restarting exposure..." message appears after about 1-2 successful exposures. In this case, it does not seem to recover itself and I have to stop/start the sequence to get it to progress. During these situations, the following information is provided in gdb, the double free always appears right before the restart but not after successful exposures as far as I can tell:
2024-04-03T07:56:11: Driver indi_gphoto_ccd: free(): double free detected in tcache 2
2024-04-03T07:56:16: Driver indi_gphoto_ccd: read EOF
<delProperty device="GPhoto CCD"/>
2024-04-03T07:56:16: Driver indi_gphoto_ccd: restart #8

I did get a crash in capture code at one point while running under gdb, though it does not always crash, so could have been bad state from trying something else:
#0  0x00007ffff71bf32c in ?? () from /usr/lib/libc.so.6
#1  0x00007ffff716e6c8 in raise () from /usr/lib/libc.so.6
#2  0x00007ffff71564b8 in abort () from /usr/lib/libc.so.6
#3  0x00007ffff7157395 in ?? () from /usr/lib/libc.so.6
#4  0x00007ffff71c92a7 in ?? () from /usr/lib/libc.so.6
#5  0x00007ffff71cb799 in ?? () from /usr/lib/libc.so.6
#6  0x00007ffff71cde93 in free () from /usr/lib/libc.so.6
#7  0x00007ffff4d8a4f8 in ?? () from /usr/lib/libgphoto2/2.5.31/ptp2.so
#8  0x00007ffff4d3f30b in ?? () from /usr/lib/libgphoto2/2.5.31/ptp2.so
#9  0x00007ffff7e98398 in gp_camera_capture () from /usr/lib/libgphoto2.so.6
#10 0x00005555555788e4 in stop_bulb (arg=0x55555564cd50) at /home/user/Downloads/indi-3rdparty/indi-gphoto/gphoto_driver.cpp:670
#11 0x00007ffff71bd55a in ?? () from /usr/lib/libc.so.6
#12 0x00007ffff723aa3c in ?? () from /usr/lib/libc.so.6

I am on Arch, Linux 6.8.2 x86-64 and have the following software/packages installed:
  • kstars 3.6.9 Stable from the Arch extra repository
  • INDI Library 2.0.6 from extra repository
  • INDI 3rd Party GPhoto CCD at cd5aac9 (2.0.7) from git
  • gphoto2 2.5.28 from extra repository
  • libgphoto2 2.5.31 from extra repository
  • libgphoto2_port 0.12.2 from extra repository

Quick edit to add I've quickly tried KStars 3.7.0 and INDI 2.0.7 (plus cleaned/recompiled GPhoto CCD driver) and noticed no difference in behavior preliminarily.

I think when KStars eventually does crash after several attempts to recover, I end up with segfaults in dmesg, but they do not appear every time the driver crashes:
[189688.296478] kstars[401744]: segfault at 55bf00000020 ip 000055bfba35d6e8 sp 00007fffb706a3c0 error 4 in kstars[55bfb9dde000+c90000] likely on CPU 19 (core 9, socket 0)
[189688.296492] Code: 00 48 8d 44 24 28 48 89 04 24 e8 e3 69 59 00 0f b6 40 10 84 c0 0f 85 57 04 00 00 49 8b 06 48 8b 7c 24 08 48 8d 35 1f dc 71 00 <48> 8b 40 20 8b 40 04 85 c0 48 8d 44 24 28 48 89 04 24 0f 85 50 03
[190554.326715] indi_gphoto_ccd[427190]: segfault at 0 ip 00007ffff71cd8b7 sp 00007fffefdff460 error 4 in libc.so.6[7ffff7156000+15b000] likely on CPU 21 (core 11, socket 0)
[190554.326730] Code: 00 00 00 0f b7 0c 6a 66 85 c9 0f 84 12 ff ff ff 48 8d 7d 10 48 8b 04 fa a8 0f 0f 85 93 01 00 00 48 89 c6 83 e9 01 48 c1 ee 0c <48> 33 30 48 89 34 fa 66 89 0c 6a 48 c7 40 08 00 00 00 00 48 83 c4
[192958.190197] kstars[464048]: segfault at 601300000020 ip 000060133e9b96e8 sp 00007ffe51596480 error 4 in kstars[60133e43a000+c90000] likely on CPU 5 (core 5, socket 0)
[192958.190211] Code: 00 48 8d 44 24 28 48 89 04 24 e8 e3 69 59 00 0f b6 40 10 84 c0 0f 85 57 04 00 00 49 8b 06 48 8b 7c 24 08 48 8d 35 1f dc 71 00 <48> 8b 40 20 8b 40 04 85 c0 48 8d 44 24 28 48 89 04 24 0f 85 50 03

I have tried repeatedly issuing a --capture-image-and-download with gphoto2 and have not been able to get it to fail at various exposure lengths even after issuing the command in a loop over several minutes.

Any suggestions?
The following user(s) said Thank You: Edoardo
Last edit: 1 month 3 hours ago by Jason Ashley. Reason: Fix code blocks
1 month 9 hours ago #100057
Attachments:

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

Time to create page: 0.284 seconds