Closed Bug 169236 Opened 22 years ago Closed 8 years ago

resource/memory failure [@ SetFont(...aFont=0...)] in Phoenix

Categories

(Core :: Layout: Text and Fonts, defect)

x86
Windows 98
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: timeless, Assigned: dbaron)

References

()

Details

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.1b) Gecko/20020912 [Phoenix] p133, 32mb ram, 0 mb free disk space (swap had grown to fill the disk, so i suspect that the os ran out of memory) I didn't have drwatson running and i didn't have talkback because phoenix doesn't do that. The crash happened after i had stopped a bugzilla page load and decided to go back or forward, i was using 3 tabs (the window had 5 tabs at some point in time). I sent dbradley the windows crash output and he was able to connect it to a specific line of code. Essentially we believe that an allocation failed for the aFont parameter to SetFont.
The crash is occuring on line 1924 of nsRuleNode.cpp aFont was null at this point and that caused the crash. The most I can tell is that nsRuleNode::ComputeFontData called SetFont, using font. Given timeless's comment this was an out of memory condition and the code didn't check the final new for font. Here's the crash data Timeless had: EAX=00000001 CS=0167 EIP=00f8b2f5 EFLGS=00010246 EBX=030d7670 SS=016f ESP=0065d0cc EBP=0065d0e0 ECX=00000032 DS=016f ESI=00000000 FS=41b7 EDX=00000033 ES=016f EDI=0065d1e8 GS=0000 Bytes at CS:EIP: 88 46 14 8b 47 10 3b c2 75 11 3b c1 74 08 3b c2 Stack dump: 00bd694c 02a70dcc 00000000 030d76d0 030d76b0 0065d144 00f8b042 030d7670 0275db9c 00000000 00000001 00000000 00000000 0065d1e8 030d76b0 00bd694c
QA Contact: petersen → moied
Component: Layout → Layout: Fonts and Text
QA Contact: moied → ylong
QA Contact: amyy → layout.fonts-and-text
Comment 2 blames "out of memory condition" so I'm guessing this is something that we'd intentionally abort for these days.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.