[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 127828] New: Editing within parentheses causes 100% CPU usage -
From:       Will Briggs <will () burnieanglican ! org ! au>
Date:       2006-05-22 14:23:26
Message-ID: 20060522162322.127828.will () burnieanglican ! org ! au
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=127828         
           Summary: Editing within parentheses causes 100% CPU usage -
                    perhaps PHP files only
           Product: kdevelop
           Version: 3.3.2
          Platform: Gentoo Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: will burnieanglican org au


Version:           3.3.2 (using KDE KDE 3.5.2)
Installed from:    Gentoo Packages
Compiler:          gcc version 3.4.6  (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9) \
                x86_64
OS:                Linux

It happens after a while - sometimes 5-10 minutes of editing, sometimes a little bit \
later - makes me think it's a leak of some sort. I'm editing a file (I've only \
noticed the behaviour with PHP files). A certain points in the editing CPU usage hits \
100% and everything grinds to a halt. The "certain points" are when editing is being \
done within parentheses.

So, if I want to enter the line "$x = somefunc("blah");" everything is fine typing \
"$x = somefunc(" and then everything slows down until the closing ")" is entered. \
Similarly if I typed "$x = somefunc()" and then went back to insert the "blah" \
between the parentheses then the problem would still happen.

The symptoms persist even if the parentheses are not part of the code
e.g. the line "$str = "some string with a (".$var.")"; would be slow betweeen the \
opening and closing parentheses.

Can't think of any further diagnostics - it's one of those ones that are difficult to \
reproduce precisely.


[prev in list] [next in list] [prev in thread] [next in thread]