Closed
Bug 380451
Opened 17 years ago
Closed 17 years ago
Store hashcode in textrun to avoid accessing deleted text
Categories
(Core :: Graphics, defect)
Core
Graphics
Tracking
()
RESOLVED
FIXED
People
(Reporter: roc, Assigned: roc)
Details
Attachments
(1 file)
8.13 KB,
patch
|
vlad
:
review+
|
Details | Diff | Splinter Review |
When nsTextFrameThebes uses TEXT_IS_PERSISTENT to avoid maintaining a separate copy of DOM text in the textrun, we have a problem when the DOM text changes. We need to destroy the textrun and remove it from the cache, but gfxTextRunCache::RemoveTextRun needs the hashcode of the text to find the entry to remove, but the text is already gone so we get the wrong hashcode or we crash on invalid memory.
Assignee | ||
Comment 1•17 years ago
|
||
We can't remove the textrun before the text changes, because there is no DOM notification for that (and adding one could be costly). So instead I just store the hashcode in the textrun so we can always get it and find the hash entry for the textrun.
Attachment #264535 -
Flags: review?(vladimir)
Attachment #264535 -
Flags: review?(vladimir) → review+
Assignee | ||
Comment 2•17 years ago
|
||
checked in.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•17 years ago
|
Flags: in-testsuite?
You need to log in
before you can comment on or make changes to this bug.
Description
•