When digikam window is closed, the process don't die, and consumes 100% of resources.

[Maik Qualmann]

Either you test digiKam-8.4.0 from git/master or try the patch.

Maik

Am Mittwoch, 24. April 2024, 21:15:06 MESZ schrieben Sie:
> The cause is probably the ExifTool Process, which is ended by a different
> thread than the one it was created by, I'll change something.
> 
> Maik
> 
> Am Mittwoch, 24. April 2024, 20:43:19 MESZ schrieb Gilles Caulier:
> > Ok, now you need to use the GDB debugger to identify where the crash
> > occurs. All is explained in Contribute web page :
> > 
> > https://www.digikam.org/contribute/
> > 
> > Note : the crash is not reproducible at all here with current code.
> > Gilles Caulier
> > 
> > Le mer. 24 avr. 2024 à 19:07, Benoît Barbier <benoitlst at ouvaton.org> a
> > écrit> 
> > > Thanks for your help
> > > I got a log file of 792054 lines.
> > > All identical until the end of the log file
> > > Thousands of times :
> > > QSocketNotifier: Invalid socket 82 and type 'Read', disabling...
> > > 
> > > Here's the head of the file
> > > 
> > > 
> > > --
> > > Benoît
> > > 
> > > Le 24/04/24 à 17:55, Gilles Caulier a écrit :
> > > > export QT_LOGGING_RULES="digikam*=true" && digikam

-------------- next part --------------
A non-text attachment was scrubbed...
Name: exitExifTool.patch
Type: text/x-patch
Size: 469 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20240424/1a412ffc/attachment.bin>