Closed Bug 199016 Opened 22 years ago Closed 22 years ago

Crash at startup in nsBlender.cpp

Categories

(Core Graveyard :: GFX, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 198946

People

(Reporter: tenthumbs, Assigned: kmcclusk)

Details

Attachments

(2 files)

Updated my tree this morning. Did a debug build with gcc 3.2.2 and get this at
startup before any windows appear.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 13503)]
0x408d2e7e in ComputeAlphasByByte (aNumLines=100, aBytesPerLine=400, 
    aBytesPerPixel=3, aOnBlackImage=0x82ceeb0 "", 
    aOnWhiteImage=0x82d8af8 "<FF><FF><FF>", aBytesLineSpan=400, 
    aAlphas=0x82dd000 <Address 0x82dd000 out of bounds>) at nsBlender.cpp:268
268           *aAlphas++ = (PRUint8)(255 - (*s2 - *s1));


where 0x82dd000 is the top of bss,

080a5000-082dd000 rwxp 00000000 00:00 0.

This is with no ~/.mozilla.

Stack trace upcoming.

Setting severity tp critical because of the segfault.
Attached file stack trace 1
Attached file stack trace 2
So it's not always as repeatable as one might want. :-) This is somewhat
different.
grab the patch in bug 198946 and see if that doesn't cure this.. i had some wild
crashes on startup untill i patched.
Ok, that seems to fix it. It would be nice if that bug's title were more meaningful.

Marking as duplicate.

*** This bug has been marked as a duplicate of 198946 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: