Intermittent crash in [@ NS_LogCOMPtrRelease_P | XUL @0x107843f | nsCSSStyleSheetInner::~nsCSSStyleSheetInner]

RESOLVED INVALID

Status

()

Core
CSS Parsing and Computation
--
critical
RESOLVED INVALID
6 years ago
6 years ago

People

(Reporter: emorley, Unassigned)

Tracking

({crash, intermittent-failure})

Trunk
x86_64
Mac OS X
crash, intermittent-failure
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

(Reporter)

Description

6 years ago
Rev4 MacOSX Snow Leopard 10.6 mozilla-inbound debug test jsreftest on 2012-08-20 07:45:40 PDT for push 2c4a0edcf906

slave: talos-r4-snow-041

https://tbpl.mozilla.org/php/getParsedLog.php?id=14527806&tree=Mozilla-Inbound

{
REFTEST TEST-START | file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/Regress/regress-114493.js | 1862 / 3198 (58%)
++DOMWINDOW == 24 (0x125a3a9d0) [serial = 3516] [outer = 0x12334b250]
BUGNUMBER: 114493
STATUS: Regression test for bug 114493
REFTEST TEST-PASS | file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/Regress/regress-114493.js | Section 1 of test -   item 1
REFTEST INFO | Loading a blank page
++DOMWINDOW == 25 (0x18db711d0) [serial = 3517] [outer = 0x12334b250]
TEST-UNEXPECTED-FAIL | file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/Regress/regress-114493.js | Exited with code 1 during test run
INFO | automation.py | Application ran for: 0:07:26.828149
INFO | automation.py | Reading PID log: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpbzdZ1rpidlog
Downloading symbols from: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-macosx64-debug/1345471861/firefox-17.0a1.en-US.mac64.crashreporter-symbols.zip
PROCESS-CRASH | file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/Regress/regress-114493.js | application crashed (minidump found)
Crash dump filename: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmp4bdeUT/minidumps/5F9EF3D8-D333-4A6D-8A75-86EE111FEB9A.dmp
Operating system: Mac OS X
                  10.6.8 10K549
CPU: amd64
     family 6 model 23 stepping 10
     2 CPUs

Crash reason:  EXC_BAD_ACCESS / KERN_INVALID_ADDRESS
Crash address: 0xffffffff8db6b5d0

Thread 0 (crashed)
 0  XUL!NS_LogCOMPtrRelease_P [nsTraceRefcntImpl.cpp : 1200 + 0x0]
    rbx = 0x8db70578   r12 = 0x00000000   r13 = 0x02878440   r14 = 0x8db70578
    r15 = 0x8db70520   rip = 0x02ebb379   rsp = 0x5fbfbd60   rbp = 0x5fbfbd90
    Found by: given as instruction pointer in context
 1  XUL + 0x107843f
    rip = 0x02878440   rsp = 0x5fbfbd80
    Found by: stack scanning
 2  XUL!nsCSSStyleSheetInner::~nsCSSStyleSheetInner [nsCOMPtr.h : 490 + 0x7]
    rip = 0x01c61e23   rsp = 0x5fbfbda0
    Found by: stack scanning
 3  XUL!nsCSSStyleSheetInner::RemoveSheet [nsCSSStyleSheet.cpp : 904 + 0x7]
    rip = 0x01c61f0f   rsp = 0x5fbfbdd0
    Found by: stack scanning
 4  XUL!nsCSSStyleSheet::~nsCSSStyleSheet [nsCSSStyleSheet.cpp : 1082 + 0xb]
    rip = 0x01c62397   rsp = 0x5fbfbdf0
    Found by: stack scanning
 5  XUL!nsCSSStyleSheet::~nsCSSStyleSheet [nsCSSStyleSheet.cpp : 1063 + 0x4]
    rip = 0x01c622be   rsp = 0x5fbfbe10
    Found by: stack scanning
 6  XUL!nsCSSStyleSheet::Release [nsCSSStyleSheet.cpp : 1110 + 0xb]
    rip = 0x01c628ac   rsp = 0x5fbfbe30
    Found by: stack scanning
 7  XUL!PresShell::ClearPreferenceStyleRules [nsAutoPtr.h : 862 + 0x4]
    rip = 0x01af60c3   rsp = 0x5fbfbe50
    Found by: stack scanning
 8  XUL!PresShell::Destroy [nsPresShell.cpp : 1000 + 0x7]
    rip = 0x01af5c95   rsp = 0x5fbfbe70
    Found by: stack scanning
 9  XUL!DocumentViewerImpl::DestroyPresShell [nsDocumentViewer.cpp : 4333 + 0x5]
    rip = 0x01ac5a63   rsp = 0x5fbfbea0
    Found by: stack scanning
10  XUL + 0x1075c0f
    rip = 0x02875c10   rsp = 0x5fbfbee0
    Found by: stack scanning
}
This bug was observed only on one or more of the six machines listed in
bug 787281 comment 11, which seem likely to have bad memory, disk, or
other hardware problem, based on the rate of failures on those machines
and the types of failures observed.

Therefore I'm marking this bug invalid, though it should be reopened if
it occurs on other (more reliable) hardware.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
(Assignee)

Updated

6 years ago
Keywords: intermittent-failure
(Assignee)

Updated

6 years ago
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.