Bug 121097 - kdevelop crash adding files to project
Summary: kdevelop crash adding files to project
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kdevelop
Version: 3.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-04-17 02:36 UTC by Ian Laurie
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-19 19:27:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ian Laurie 2004-04-17 02:36:41 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2)
Gecko/20040301

Description of problem:
When adding files to a project by typing their name into the
"Sourcefiles(s)" area in the "Add Existing Files(s)..." dialog box,
kdevelop effectively uses up all the cpu power, locking up the system
(making it VERY slow) and kdevelop needs to be terminated.

Adding files to a project by right clicking inside the file area in
the left window pane works fine.


Version-Release number of selected component (if applicable):
kdevelop-2.1.5-12.1

How reproducible:
Always

Steps to Reproduce:
1. Start kdevelop and open any project (or create a new one).
2. From the Project menu select "Add Existing File(s)..."
3. Try to type something into the "Sourcefile(s)" entry area.
    

Actual Results:  CPU seems to get very busy and it is hard to get the
mouse to respond.  Kdevelop is dead and will need to be terminated.

Expected Results:  Should allow you to enter a filename.

Additional info:

This bug exists in RedHat Linux 9 and Fedora Core 1 that I know of,
except under both those platforms kdevelop just exits immediately you
try and enter text.

Comment 1 RHEL Program Management 2007-10-19 19:27:25 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.


Note You need to log in before you can comment on or make changes to this bug.