Closed
Bug 382197
Opened 18 years ago
Closed 18 years ago
Hang in nsTextFrame::PeekOffsetWord
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: pavlov, Assigned: roc)
References
()
Details
When resizing the window (I think) my browser hung stuck inside of the for (;;) { } loop. wordLen is coming back as 0 so nextWordFirstChar = nextWordFirstChar + direction*wordLen; results in nextWordFirstChar == nextWordFirstChar and it never gets out.
|
||
Comment 1•18 years ago
|
||
I often get this hang when double-clicking to select words, but only with layout.word_select.eat_space_to_next_word set to TRUE (which is the default on Windows but not on other platforms).
|
|
||
Updated•18 years ago
|
Flags: blocking1.9?
|
Assignee | |
Comment 2•18 years ago
|
||
I checked in a fix that I'm pretty sure will eliminate all possible hangs in PeekOffsetWord.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
|
||
Updated•18 years ago
|
Flags: in-testsuite?
|
||
Comment 3•18 years ago
|
||
Verified that double clicking words no longer hangs Firefox on the current trunk with the new textframe enabled.
Status: RESOLVED → VERIFIED
|
|
||
Updated•16 years ago
|
Flags: blocking1.9?
You need to log in
before you can comment on or make changes to this bug.
Description
•