Bug 81027

Summary: many files open - kdevelop gets into endless loop on GUI
Product: [Unmaintained] kdelibs Reporter: Peter Somogyi <psomogyi>
Component: kmdiAssignee: Matt Rogers <mattr>
Status: RESOLVED FIXED    
Severity: crash    
Priority: NOR    
Version: SVN   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Peter Somogyi 2004-05-06 13:25:02 UTC
Version:           3.0.2 (using KDE 3.1.4)
Installed from:    SuSE
Compiler:          gcc version 3.3.1 (SuSE Linux)
OS:          Linux (i686) release 2.4.21-99-default

Many files are open. (Childframe window mode KDevelop GUI)
The filename titles almost fill the topmost toolbar.
When I open an additional file which file name is so long that it wouldn't fit into the topmost toolbar, kdevelop gets into endless loop on GUI.
(The entire screen is flickering as if it wouldn't be able to decide what to show...)
The only way after then to kill the kdevelop process.
It's a very annoying bug which exists at least from kdevelop 3.0 beta.

Workaround: I have to care about not to keep to much files open (mainly with long filenames). Unfortunately, I forget this rule very often...

Always and easily reproducable.

NOTE: I always open a file with 1 click in the file browser.
Comment 1 Matt Rogers 2004-12-30 07:14:25 UTC
Can you reproduce this with a later version of kdelibs and kdevelop? I don't quite understand your bug report because there's not a topmost toolbar that I'm aware. Thanks.
Comment 2 Peter Somogyi 2005-01-04 11:50:22 UTC
I've upgraded a different system (RedHat 9.0) to KDE 3.3.0, and setup KDevelop 3.1.0, and now I cannot reproduce the error.
So that this bug seems to be resolved.

Note: you can have that file list toolbar when you set Settings/Configure KDevelop/User Interface/IDEAl window mode (restarting KDevelop). The file names appear on this toolbar which are open (each having a tab button). It's just above the editor window.
Comment 3 Andreas Kling 2006-07-25 10:05:43 UTC
Closing as per comment #2.