[SeaMonkey, Windows] 'make mailbloat' crashes on "TB Try", on "RDFServiceImpl::GetResource()"

NEW
Unassigned

Status

--
major
7 years ago
6 years ago

People

(Reporter: sgautherie, Unassigned)

Tracking

(Blocks: 2 bugs, {crash, regression})

Trunk
x86
Windows Server 2003
crash, regression
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
(In reply to Serge Gautherie (:sgautherie) from bug 523773 comment #5)
> Fixed on SM 2.10, as expected.

I have no idea what/when regressed this.

*****

Old VC8 build:

https://tbpl.mozilla.org/?tree=Thunderbird-Try&rev=1839e33db464
https://tbpl.mozilla.org/php/getParsedLog.php?id=11483473&tree=Thunderbird-Try
TB WINNT 5.2 try-comm-central leak test build on 2012-05-04 15:12:52 PDT for push 1839e33db464
{
PROCESS-CRASH | bloatTests | application crashed (minidump found)

TEST-UNEXPECTED-FAIL | runtest.py | Exited with code -2147483645 during test run

Crash reason:  EXCEPTION_BREAKPOINT

Thread 0 (crashed)

 3  xul.dll!RDFServiceImpl::GetResource(nsACString_internal const &,nsIRDFResource * *) [nsRDFService.cpp:495e6cd1903d : 922 + 0x29]
    eip = 0x025d4acf   esp = 0x0012b8a4   ebp = 0x0012b9e0
    Found by: call frame info
[...]

make: *** [mailbloat] Error 1
}
(Reporter)

Comment 1

7 years ago
https://tbpl.mozilla.org/?tree=Thunderbird-Try&rev=cc0c38956067
https://tbpl.mozilla.org/php/getParsedLog.php?id=11487365&tree=Thunderbird-Try
TB WINNT 5.2 try-comm-central leak test build on 2012-05-04 18:33:24 PDT for push cc0c38956067

Same.
(Reporter)

Comment 2

7 years ago
New VC10 build:

https://tbpl.mozilla.org/?tree=Thunderbird-Try&rev=d8840d093e57
https://tbpl.mozilla.org/php/getParsedLog.php?id=11613538&tree=Thunderbird-Try
TB WINNT 5.2 try-comm-central leak test build on 2012-05-09 09:55:38 PDT for push d8840d093e57

Same.

Comment 3

6 years ago
Cleaning up/fixing whiteboards containing 'orange' but not '[orange]' in advance of bug 791758.
Whiteboard: [would-be perma-orange]
You need to log in before you can comment on or make changes to this bug.