Closed Bug 587189 Opened 15 years ago Closed 14 years ago

valgrind - Stack overflow - layout/base/crashtests/457362-1.xhtml

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
blocking2.0 --- -

People

(Reporter: bc, Unassigned)

References

Details

(Keywords: crash, regression, valgrind)

REFTEST TEST-START | file:///work/mozilla/builds/2.0.0/mozilla/layout/base/crashtests/457362-1.xhtml ++DOMWINDOW == 16 (0xfd25628) [serial = 1523] [outer = 0x9ce3dc0] --DOMWINDOW == 15 (0xfe83198) [serial = 1513] [outer = 0x9ce3dc0] [url = file:///work/mozilla/builds/2.0.0/mozilla/layout/base/crashtests/455063-2.html] --DOMWINDOW == 14 (0x172c49f8) [serial = 1522] [outer = 0x9ce3dc0] [url = data:text/html,%3C%21%2D%2DCLEAR%2D%2D%3E] ==32735== Stack overflow in thread 1: can't grow stack to 0x7fe601968 ==32735== Can't extend stack to 0x7fe600dc0 during signal delivery for thread 1: ==32735== no stack segment ==32735== ==32735== Process terminating with default action of signal 11 (SIGSEGV) ==32735== Access not within mapped region at address 0x7FE600DC0 ==32735== at 0x58F7610: nsLineBreaker::AppendText(nsIAtom*, unsigned char const*, unsigned int, unsigned int, nsILineBreakSink*) (nsLineBreaker.cpp:268) ==32735== If you believe this happened as a result of a stack ==32735== overflow in your program's main thread (unlikely but ==32735== possible), you can try to increase the size of the ==32735== main thread stack using the --main-stacksize= flag. ==32735== The main thread stack size used in this run was 10485760.
Blocks: sisyphus-valgrind
Summary: Stack overflow - layout/base/crashtests/457362-1.xhtml → valgrind - Stack overflow - layout/base/crashtests/457362-1.xhtml
Possibly related to Bug 591898? (There was *some* albeit relatively minor research on this issue there)
Blocks: 591898
blocking2.0: --- → ?
What does the stack look like?
Are you even confident this is a stack overflow? Those error messages make me uncertain.
(In reply to comment #3) > What does the stack look like? I don't have it available. (In reply to comment #4) > Are you even confident this is a stack overflow? Those error messages make me > uncertain. No. I'm not certain. It was the first time I had ever seen that message. We can make this incomplete or some other resolution until I can get more information.
I couldn't repro any warnings on this testcase, so at the very least I'm going to say this isn't a blocker.
blocking2.0: ? → -
related to Bug 520028 ?
update crash bugs to critical per guidelines.
Severity: normal → critical
bc, is this bug still useful/happening or should it be closed?
Not seen in recent history and only the old man in the cave has any memory of it at all. -> WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Issue is resolved - clearing old keywords - qa-wanted clean-up
Keywords: regressionwindow-wanted
You need to log in before you can comment on or make changes to this bug.