[Digikam-devel] [Bug 290961] digiKam crashes after closing the configure dialog

[Deep-Sea]

https://bugs.kde.org/show_bug.cgi?id=290961





--- Comment #7 from Deep-Sea <Deep-Sea gmx net>  2012-01-08 20:18:33 ---
To check the questions and use debugview, I do new tests. At the first test,
digiKam don't freeze! And I don't know why, I have change nothing. But at the
second test, all was like before.

> How long do you wait before you kill it?
A few minutes at the old test.
30 Minutes at the second test. But then I press Ctrl + C at the gdb console and
can type "bt" (and "quit"). The output:

[New Thread 412.0x16a8]

Program received signal SIGINT, Interrupt.
[Switching to Thread 412.0x16a8]
0x76e3e37d in KERNEL32!FormatMessageW () from C:\Windows\system32\kernel32.dll
#0  0x76e3e37d in KERNEL32!FormatMessageW ()
   from C:\Windows\system32\kernel32.dll
#1  0x76e0ed6c in KERNEL32!AcquireSRWLockExclusive ()
   from C:\Windows\system32\kernel32.dll
#2  0x773437f5 in ntdll!RtlInsertElementGenericTableAvl ()
   from C:\Windows\system32\ntdll.dll
#3  0x773437c8 in ntdll!RtlInsertElementGenericTableAvl ()
   from C:\Windows\system32\ntdll.dll
#4  0x00000000 in ?? ()
A debugging session is active.

    Inferior 1 [process 412] will be killed.

Quit anyway? (y or n) 



> Also, during all of this does your hard drive have high disk-activity?
No.

> Does it say "Scanning collection0%" at the bottom-left of digiKam's main window?
No.



debugview shows no new entries after digiKam was started. Do you want the
complete log file anyway?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.