Open garz75 opened 1 month ago
I'm not sure if this is something I can fix but will take a look at the python subprocess module to see if I'm missing something. When exiftool is first called, a persistent exiftool process is started in a subprocess and the osxphotos python code then communicates with this process to run the exiftool commands. This prevents having to start a new exiftool process for every photo. There is tear-down code that will kill any lingering exiftool processes at shutdown but of course, this doesn't get called if you kill the python process or it segfaults.
@all-contributors please add @garz75 for bug
@RhetTbull
I've put up a pull request to add @garz75! :tada:
Describe the bug
When the main exiftool python process is killed abruptly (SEGFAULT or kill -9), the perl process started for exiftool keeps running (see screenshots). I am not sure if it is an exiftool bug or an osxphotos bug: when the osxphotos process is killed, the perl process should receive a signal (SIGPIPE, if I remember my college Unix courses correctly), and exit by itself...
To Reproduce
osxphotos export
with the--exiftool
argument (see below the full command line used if needed)Expected behavior
The perl process should exit or be killed
Screenshots
Command line used:
Lingering perl processes after 3 SEGFAULTS and one
kill -9
:Note: The segfaults I mention were due to a faulty python installation, it is not a bug in osxphotos. Upgrading python with homebrew fixed the issue....
Desktop (please complete the following information):