Closed Bug 913008 Opened 12 years ago Closed 12 years ago

Daily x64 2013-09-05-04-59-33-comm-central will not start in Win x64

Categories

(Thunderbird :: General, defect)

Product:
Thunderbird
Component:
General
Platform:
x86_64
All
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: mike-foerster, Unassigned)

References

Details

(Keywords: crash, regression)

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:26.0) Gecko/20100101 Firefox/26.0 (Beta/Release) Build ID: 20130903030201 Steps to reproduce: Daily updated automatically Version 26.0a1 from App-ID 20130904030204 (2013-09-04) to latest version (2013-09-05) Actual results: Application did not start automatically. (It is also impossible to start the application manually) Expected results: Automatic start after update
Are you using the 64bit build? I am running it on Win 7 64bit and it won't start as you describe, however the 32bit version will
I am using 64bit build on Windows 8 and I have the same problem.
I can confirm this is happening in the latest (2013-09-05) x64 build under Win8. Partial stack trace reports: Unhandled exception at 0x000007FCF7771CDC (mozjs.dll) in thunderbird.exe: 0xC0000005: Access violation reading location 0x000000A0000004EC.
Severity: normal → critical
Keywords: crash, regression
This is happening to me on Windows 8.0 Professional x64 (plain RTM with recent updates). Observations: 1. On the nightly build server, the builds in "2013-09-04-03-02-04-comm-central" are working fine 2. Of very next builds in "2013-09-05-04-59-33-comm-central", the 32 bit version runs fine but the 64 bit version crashes. 3. The crash is 100% reproducible and always happens before the main window becomes visible. Debugging the process yields an 0xC0000005 access violation in mozjs.dll at 0x7FA8767A462, accessing memory location 0x2D (looks like a null-pointer access to some structure member with an offset of 45 decimal). No idea if it helps, but: 000007FA843EA43C mov r12,qword ptr [rcx+2C0h] 000007FA843EA443 mov rcx,rbx 000007FA843EA446 call qword ptr [rax] 000007FA843EA448 mov r8d,eax 000007FA843EA44B mov esi,eax 000007FA843EA44D mov dword ptr [rsp+28h],eax 000007FA843EA451 imul r8d,r8d,9E3779B9h 000007FA843EA458 cmp r8d,1 000007FA843EA45C ja 000007FA843EA462 000007FA843EA45E add r8d,0FFFFFFFEh 000007FA843EA462 mov rcx,qword ptr [r12+28h] ; <-- crash here, r12 is 5
Confirming this on Win 7 x64 with x64 nightly builds. I didn't report this sooner because I thought it must be some glitch that would be resolved in latest builds after 2013-09-05-04-59-33-comm-central. Unfortunately, there is no x64 build for windows since then.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Daily Version 26.0a1update of 2013-09-05 will not start in Win 8.1 Preview → Daily x64 2013-09-05-04-59-33-comm-central will not start in Win x64
I just noticed this is filed against the installer component and WinNT (which refers to the actual version of the OS AFAIK - not the NT family of OSes). Lets see if it gets more attention now.
Component: Installer → General
OS: Windows NT → All
Hardware: x86 → x86_64
Version: 26 → Trunk
(In reply to Ludovic Hirlimann [:Usul] from comment #9) > Is this bug 915571 ? No, bug 915571 is a compilation failure. This isn't.
I don't know if it was bug 915571 or something else that fixed this, but the issue is no more with yesterdays build (2013-09-12-11-58-27-comm-central). Please confirm.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
...PS: there were no intermediate Win x64 builds between 2013-09-05-04-59-33-comm-central and 2013-09-12-11-58-27-comm-central. So whatever fixed is was in the latest commit and what caused it was between 2013-09-04-03-02-04-comm-central and 2013-09-05-04-59-33-comm-central.
Confirmed - This issue is now resolved. Yay!
-> WFM (as we don't know what patch fixed it)
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.