Closed Bug 1127260 Opened 9 years ago Closed 5 years ago

crash in nsRect::UnionRect(nsRect const&, nsRect const&)

Categories

(Core :: General, defect)

All
macOS
defect
Not set
critical

Tracking

()

RESOLVED WONTFIX

People

(Reporter: daniela.domnici, Unassigned)

References

Details

(Keywords: crash, steps-wanted)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-36121f00-42d6-4779-9e31-f955a2150129.
=============================================================
We had this crash when running our central-remote testruns

Reports:  http://mozmill-daily.blargon7.com/#/remote/report/6b1e6b9bf618fb20da2bf872749e0c5ez
The crash line in nsTextFrame::ReflowText():
   8450 aMetrics.SetOverflowAreasToDesiredBounds();
 > 8451 aMetrics.VisualOverflow().UnionRect(aMetrics.VisualOverflow(), boundingBox);

all the nsRects there are known to be allocated.  I don't see any way that that line
could crash.  Also the crash data says:
Crash Reason:	EXC_BREAKPOINT / 0x00000002
Crash Address:	0x1021e53f1

Note that the address is an odd number.  None of the fields in an nsRect are
at an odd address ever.  The crash reason also looks a bit unusual to me.

I don't think the layout code is at fault here.  This crash looks more like
some thread or signal issue.  Perhaps some other process or OSX sent us
signal 2 for some reason.  The default action is to terminate:
https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man3/signal.3.html
Component: Layout → General
Blocks: 1127292
Blocks: 1127361
Blocks: 1132043
Crash Signature: [@ nsRect::UnionRect(nsRect const&, nsRect const&)] → [@ nsRect::UnionRect(nsRect const&, nsRect const&)] [@ nsRect::UnionRect]
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Closing because no crashes reported for 12 weeks.
You need to log in before you can comment on or make changes to this bug.