Closed Bug 183531 Opened 23 years ago Closed 21 years ago

Chimera crashed for indeterminate reason [@ nsRenderingContextMac::SetClipRegion]

Categories

(Camino Graveyard :: General, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bugmail, Assigned: sfraser_bugs)

Details

(Keywords: crash)

Crash Data

Attachments

(1 file)

Chimera/2002112604 just crashed for me and generated a new (for me, anyway) stack, crashing at MaxScanLineInversionPoints. (Stack to be attached, also reported as TB75139W.) Unfortunately, I'm not sure what I was doing at the time. I had a few tabs open showing Bugzilla bugs, and had been dragging links to tabs, but I think this may have happened while simply waiting for a bug to display.
Keywords: crash
Summary: Chimera crashed for indeterminate reason → Chimera crashed for indeterminate reason [@ MaxScanLineInversionPoints]
was it just sitting there when it crashed or loading a page? ->sfraser, drawing crash
Assignee: saari → sfraser
This one shows up quite frequently on the talkback reports. It might be related to bug 182384, but the odd thing is that inside [ChildView drawRect] the current port should be good.
Status: NEW → ASSIGNED
Summary: Chimera crashed for indeterminate reason [@ MaxScanLineInversionPoints] → Chimera crashed for indeterminate reason [@ nsRenderingContextMac::SetClipRegion]
Anyone seen this recently?
I think we can savely close this bug since there hasn't been any report of crashes alike for almost 1 1/2 years now.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Crash Signature: [@ nsRenderingContextMac::SetClipRegion]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: