Closed Bug 395335 Opened 17 years ago Closed 17 years ago

Changing text in <xul:tree> triggers "ASSERTION: Invalid offset"

Categories

(Core :: Graphics, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jruderman, Assigned: roc)

References

Details

(Keywords: assertion, testcase)

Attachments

(2 files)

317 bytes, application/xhtml+xml
Details
202 bytes, application/xhtml+xml
Details
Reloading the testcase triggers:

###!!! ASSERTION: Invalid offset: 'aOffset <= mSkipChars->mCharCount', file /Users/jruderman/trunk/mozilla/gfx/thebes/src/gfxSkipChars.cpp, line 92
###!!! ASSERTION: Substring out of range: 'aStart + aLength <= mCharacterCount', file /Users/jruderman/trunk/mozilla/gfx/thebes/src/gfxFont.cpp, line 1045

Also, the display is incorrect.  Firefox should display the new text 'xyz' but instead it continues to display the old text 'a'.
Flags: blocking1.9?
Attached file testcase
Attached file reference
Assignee: nobody → roc
(In reply to comment #0)
>Also, the display is incorrect.  Firefox should display the new text 'xyz' but
>instead it continues to display the old text 'a'.
Actually, it shouldn't display either text; at least, older builds don't.
How long ago did Firefox start displaying the text?
I don't have any builds in between, but 20070619 doesn't display the text.
Blocks: textfuzzer
Flags: blocking1.9? → blocking1.9+
This works for me on Mac. We display the text and don't assert. Anyone confirm?
WFM on Linux, no assert and text is displayed.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
WFM.  Should I check in the files here as a reftest pair?
Flags: in-testsuite?
I think we should probably just check in the testcase as a "crash/assert/leak test" when the work in bug 399830 is done.
Crashtest checked in.
Flags: in-testsuite? → in-testsuite+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: