https://bugs.kde.org/show_bug.cgi?id=407745
Knut Hildebrandt <knut.hildebra...@gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |knut.hildebra...@gmx.de
--- Comment #2 from Knut Hildebrandt <knut.hildebra...@gmx.de> ---
Same on Chakra Linux.
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
In my case kdiff3 does not always crash, but only if comparing directories
containing many or huge files. I also did not get the segmentation fault.
And kdiff3 actually more often hangs than crashes. If it hangs this can happen
at any moment of comparison, at 17%, 50% or even 99%.
All above said holds true for "Binary comparison".
Using "Fuall analysis" I got this output on crashing:
$ kdiff3
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
KCrash: Application 'kdiff3' crashing...
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
Using "Trust size and date but use binary ..." the output looked like that:
$ kdiff3
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
Unable to start Dr. Konqi
Re-raising signal for core dump handling.
The per-process limit on the number of open file descriptors has been reached.
ERROR: cannot create wakeup pipe
"Trust size" and "Trust size and modification date" worked fine.
--
You are receiving this mail because:
You are watching all bug changes.
