https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #18 from Maik Qualmann ---
We'll see if the problem persists with the next bundle. This will have debug
disabled by default unless an environment variable is set.
This code should no longer be executed in the TIFF Loader:
https://invent.kde
https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #17 from k...@binkmail.com ---
Sorry guys. Guess I should have tried this sooner.
I ran digikam with sysinternals dbgview and it logged a few hundred lines.
TIFFPrintDirectory(tif, stdout, 0);
Is going to stdout and QT under windows some
https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #16 from Maik Qualmann ---
Git commit 0772bc4d53487eeb36b160b8d122d0b21be45714 by Maik Qualmann.
Committed on 19/02/2022 at 07:02.
Pushed by mqualmann into branch 'master'.
backport from qt5-maintenance to enable logging optional
M +1
https://bugs.kde.org/show_bug.cgi?id=426086
Maik Qualmann changed:
What|Removed |Added
Version Fixed In||7.6.0
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #14 from Maik Qualmann ---
Ok, I'll create an option to turn debugging on/off in the system settings.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #13 from caulier.gil...@gmail.com ---
Maik,
The DEBUG pre-compiler directive will not work.
All codes for the bundles are always compiled with debug symbols. At last stage
when bundles are packaged, we strip or not the debug symbols in bina
https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #12 from k...@binkmail.com ---
(In reply to Maik Qualmann from comment #9)
> Ok, now I understand after looking at the source code. I'm very surprised
> that this debug rules is supposed to slow down digiKam so much.
I patched the release bu
https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #11 from Maik Qualmann ---
Gilles,
I think we could add a "defined DEBUG" here to only have the output in the
debug bundle.
https://invent.kde.org/graphics/digikam/-/blob/master/core/app/utils/digikam_debug.cpp#L81
Maik
--
You are recei
https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #10 from caulier.gil...@gmail.com ---
Maik,
I set this rules for Windows and MacOS, especially for Windows where setting
the env. variables is more complex than under Linux.
I suppose that debug trace must pass by the Windows kernel and tak
https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #9 from Maik Qualmann ---
Ok, now I understand after looking at the source code. I'm very surprised that
this debug rules is supposed to slow down digiKam so much.
Maik
--
You are receiving this mail because:
You are watching all bug chan
https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #8 from Maik Qualmann ---
Which digiKam Windows EXE are you using? If you use the one with "debug" in the
filename it would explain it. You should definitely install the smaller
installer without "debug" in the filename.
Maik
--
You are r
https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #7 from k...@binkmail.com ---
Can't believe I had to find and fix this myself.
I wondered why the stack trace contained msvcrt.dll!putc then I wondered why it
contained libtiff-5.dll!TIFFPrintDirectory then I looked at the source and find
o
https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #6 from k...@binkmail.com ---
(In reply to caulier.gilles from comment #5)
> Did you have the metadata view open in right sidebar, and especially the
> ExifTool tab ?
Nope. Usually filters and I just checked and exiftool isn't running.
I h
https://bugs.kde.org/show_bug.cgi?id=426086
caulier.gil...@gmail.com changed:
What|Removed |Added
Version|7.1.0 |7.6.0
--- Comment #5 from caulier.gil
https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #4 from k...@binkmail.com ---
This problem went away at some point but has returned even worse in 7.5 and the
most recent 7.6.
Here hopefully
https://ufile.io/er79cpxm
will get you a photoshop saved16bit tiff file. I have a dozen applica
https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #3 from k...@binkmail.com ---
More observation. Viewing one of these files in the digiKam slideshow takes
about 2 minutes to load and digiKam memory usage slowly increases by about
600MB during that 2 minutes then falls back to about the orig
https://bugs.kde.org/show_bug.cgi?id=426086
--- Comment #2 from k...@binkmail.com ---
Bit hard for me to tell what is going on especially when it is easy to have
these files in the system disk cache which hides the problem and difficult to
know it is in the cache.
Seems to be related to addition
https://bugs.kde.org/show_bug.cgi?id=426086
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
https://bugs.kde.org/show_bug.cgi?id=426086
caulier.gil...@gmail.com changed:
What|Removed |Added
Platform|Other |Microsoft Windows
CC|
19 matches
Mail list logo
