Summary: | Typing into "Enter Tag Here" crashes digikam 100% of the time | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Claudius <kde.bugs> |
Component: | Tags-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | caulier.gilles, metzpinguin |
Priority: | NOR | ||
Version: | 4.10.0 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | 4.12.0 | |
Sentry Crash Report: |
Description
Claudius
2015-05-31 16:16:17 UTC
We need a trace to hack using debugview.exe. See details on this page : https://www.digikam.org/contrib Gilles Caulier The page says (paraphrased) "you need to run a debug version" - there is no such version for windows. There are also no build instructions so I could build my own digikam with debug symbols. (ticket https://bugs.kde.org/show_bug.cgi?id=342481 pending). You need to run debugview.exe to show debug traces printed on the console (not visible by default). It's not debug symbols, it's debug strings printed at run time... debugview does produce output like this from DigiKam around 100 lines at startup, the last of them like this: > 00000078 23:04:05 [5848] digikam(5848)/digikam (core) class Digikam::ThumbnailImage __thiscall Digikam::ThumbnailCreator::createThumbnail(const class Digikam::ThumbnailInfo &,const class QRect &) const: Cannot create thumbnail for "C:/Users/name/dir/Android Camera/2008/MOV00003.3GP" > 00000079 23:04:05 [5848] digikam(5848)/digikam (core) class QImage __thiscall Digikam::ThumbnailCreator::load(const class Digikam::ThumbnailIdentifier &,const class QRect &,bool) const: Thumbnail is null for "C:/Users/name/dir/Android Camera/2008/MOV00003.3GP" But it does nothing at the point where the program freezes. No Stacktrace, nothing. The Program just grays out[1] and a message appears if i want to wait or close the program. I can wait for an hour and this does not resolve itself. I can close the program, but i don't get anything like a stack trace out of it. [1]: looks like this http://imgur.com/31IPaql i managed to get Visual Studio connected to my digikam process. It's not particularly helpful, though. When the application is grayed out, and i pause it in VS, the stack is full of QtGui and QtCore, but it does not run deep enough to find out where it goes. http://imgur.com/pE7p5J3 Also, when digikam goes into that state, it grabs one cpu core for itself. any other hint, how i could help debug this? sorry for bumping this, but i have no idea how else to proceed. *bump* Did you write metadata to image ? Check Setup/metadata config panel... Gilles Caulier Yes i do (my metadata settings screen: http://imgur.com/soTxWQv ) I wonder if this is the issue, though. At that point in time, there's not yet anything selected to write to the file. I'm not yet confirming any tag. This really happens in the instant i start typing - where i wouldn't even have completed a tag to insert into the file. On text field, show popup menu with right mouse button and disable check spelling. Gilles Caulier There's no spell checking option in the context-menu ( that's what it looks like on my system, including one expanded submenu http://imgur.com/T8EOIIj ) for testing, i removed auto-complete (set it to "none") it did not help, either. Disable text completion well... Gilles Caulier Yes i did. It did not help, nor did other text-completion settings i tried. Whenever the first character is typed (and i don't even see it appear in the text-field!) the program freezes. I hope this issue will resolve itself with 5.0 :-( *bump* Did you try to backup your database, remove it, restart digiKam, repopulate it and try again ? Gilles Caulier as mentioned in the original post, i tried with a completely empty database with just a few images imported. It happens always. With "my" database, with an empty new database. On the first try. A quick test with a VM no crash has occurred... Maik Tried a different machine (Win 8.1, though), it did not crash there. On my main machine, the crash is reproducible 100%. It even survives new databases and a complete uninstall (including registry key hunting and %AppData% folders) and reinstall. Closing it as RESOLVED/WORKSFORME for now, it's probably my setup. Thanks for the help. |