Bug 123623 - Digikam freezes or is very slow
Summary: Digikam freezes or is very slow
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Runtime (show other bugs)
Version: 0.8.1
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-14 18:00 UTC by Luciano Blini
Modified: 2017-08-15 12:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 0.9.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luciano Blini 2006-03-14 18:00:07 UTC
Version:           0.8.1 (using KDE 3.5.1 Level "a" , SUSE 10.0 UNSUPPORTED)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.13-15.8-default

Digikam crashes when I try to assign tags to a photo (or a group of photos).
I guess I've a lot of different tags (about 100, some with thumbnails, sorted in 4 / 5 main-tags).

It crash when the program tries to draw the menu: often it's slow, often the only thing to do is pressing esc key or, in the worse situation ctrl+alt+esc.
Comment 1 caulier.gilles 2006-04-03 16:11:26 UTC
Give me a backtrace using gdb and compiling digiKam with all debug information (see .configure options)

Gilles Caulier
Comment 2 Luciano Blini 2006-04-03 16:31:43 UTC
Hope it could help (I'm a newbie, I hope it's correct)

Starting program: /opt/kde3/bin/digikam
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1102384192 (LWP 8425)]
[New Thread 1105988528 (LWP 8426)]
[Thread 1105988528 (LWP 8426) exited]
[New Thread 1108089776 (LWP 8427)]
[Thread 1108089776 (LWP 8427) exited]
ASSERT: "popup->parentMenu == 0" in widgets/qpopupmenu.cpp (2300)
ASSERT: "popup->parentMenu == 0" in widgets/qpopupmenu.cpp (2300)
ASSERT: "popup->parentMenu == 0" in widgets/qpopupmenu.cpp (2300)
ASSERT: "popup->parentMenu == 0" in widgets/qpopupmenu.cpp (2300)
ASSERT: "popup->parentMenu == 0" in widgets/qpopupmenu.cpp (2300)

Program received signal SIG42, Real-time event 42.
[Switching to Thread 1102384192 (LWP 8425)]
0xffffe410 in __kernel_vsyscall ()
Comment 3 caulier.gilles 2006-04-03 18:18:33 UTC
no, you need to recompile digikam at all using the right '.configure' option : --enable-debug=full.

Gilles Caulier
Comment 4 Kjetil Borthen 2006-05-20 18:16:50 UTC
I have the same problem with both 0.8.0 and 0.8.1.

This happends if digikam are busy with listing pictures in an album at the same time that I right click on a picture and select the tag submenu.
Comment 5 caulier.gilles 2006-05-20 18:32:08 UTC
Start digiKam from a console. Have you some error messages ?

Gilles Caulier
Comment 6 Kjetil Borthen 2006-05-21 16:05:43 UTC
ASSERT: "popup->parentMenu == 0" in widgets/qpopupmenu.cpp (2301)

As well, some times the "Assign tag" submenu ("right-click-menu") stays open after the main "right-click-menu" are closed. Then I have to press ESC to get rid of it.

I have also experienced that the same "Assign tag" submenu appears when selecting "Open with".

I can confirm that this happens in version 0.8.2-beta1 as well.

Kjetil Borthen 
Comment 7 caulier.gilles 2006-07-18 10:13:47 UTC
try the last 0.8.2 tarballs, compile it using full debug option and give us a report.

http://digikam3rdparty.free.fr/0.8.2/

Thanks in advance

Gilles caulier
Comment 8 caulier.gilles 2006-07-26 15:57:54 UTC
0.9.0-beta1 is available for testing. Please give us a fresh feedback

Gilles Caulier
Comment 9 Stephen Bridges 2006-11-05 22:28:37 UTC
I have this problem in 0.9.0-beta2.  I've rebuilt a debug version in portage (Gentoo user) but as the program doesn't actually crash, there's no backtrace to report.

I'm just compiling 0.9.0-beta3 by hand with debug=full to see what I find . .
Comment 10 Stephen Bridges 2006-11-06 22:35:11 UTC
No problems in 0.9.0-beta3!
Comment 11 caulier.gilles 2006-11-07 08:11:01 UTC
Stephen, 

Well this B.K.O file can be closed. Right ?

Gilles Caulier
Comment 12 caulier.gilles 2006-11-07 18:15:39 UTC
Problem seem to be fixed with current implementation from svn

Gilles Caulier