I think I have narrowed the reason for zm 1.24.X hanging after a short period of capturing images.
Most of my debug log when zm is working describes:
06/08/09 20:59:44.056991 zmc_m1[14007].DB3-zm_remote_camera_http.cpp/196 [Read 1450 bytes]
06/08/09 20:59:44.076747 zmc_m1[14007].DB3-zm_remote_camera_http.cpp/171 [Expecting 1172 bytes]
06/08/09 20:59:44.076807 zmc_m1[14007].DB3-zm_remote_camera_http.cpp/196 [Read 1172 bytes]
06/08/09 20:59:44.095575 zmc_m1[14007].DB3-zm_remote_camera_http.cpp/166 [Socket closed]
06/08/09 20:59:44.095706 zmc_m1[14007].DB3-zm_remote_camera_http.cpp/966 [Got end of image by closure, content-length = 14222]
06/08/09 20:59:44.095765 zmc_m1[14007].DB3-zm_remote_camera_http.cpp/1004 [Returning 14222 (14222) bytes of captured content]
06/08/09 20:59:44.111682 zmc_m1[14007].DB3-zm_remote_camera_http.cpp/105 [Connected to host, socket = 5]
But every so often I get this just before zm quits capture and fails:
06/08/09 20:59:44.376817 zmc_m1[14007].DB3-zm_remote_camera_http.cpp/196 [Read 1245 bytes]
06/08/09 20:59:44.395480 zmc_m1[14007].DB3-zm_remote_camera_http.cpp/166 [Socket closed]
06/08/09 20:59:44.395607 zmc_m1[14007].DB3-zm_remote_camera_http.cpp/966 [Got end of image by closure, content-length = 14295]
06/08/09 20:59:44.395661 zmc_m1[14007].DB3-zm_remote_camera_http.cpp/979 [Trimmed end of image, new content-length = 14294]
06/08/09 20:59:44.395715 zmc_m1[14007].DB3-zm_remote_camera_http.cpp/1004 [Returning 14294 (14295) bytes of captured content]
06/08/09 20:59:44.409167 zmc_m1[14007].ERR-zm_jpeg.c/38 [Invalid JPEG file structure: two SOI markers]
06/08/09 20:59:44.410469 zmc_m1[14007].ERR-zm_remote_camera_http.cpp/1053 [Unable to decode jpeg]
06/08/09 20:59:44.410607 zmc_m1[14007].ERR-zmc.cpp/260 [Failed to capture image from monitor 1 (0/1)]
It seems zm hanging is always preceded by an attempt to trim the image which causes an invalid jpeg error.
Is there an option which controls when zmc_m1 thinks it should trim an image?