Status

()

RESOLVED INCOMPLETE
4 years ago
4 years ago

People

(Reporter: dodger.forum, Unassigned)

Tracking

({crash})

35 Branch
x86_64
Windows 8.1
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

(Reporter)

Description

4 years ago
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; .NET4.0E; .NET4.0C; rv:11.0) like Gecko

Steps to reproduce:

I close Firefox 


Actual results:

Each time when Firefox is closed Firefox crashes

Crash reports can be found here:
https://crash-stats.mozilla.com/report/index/ca40417f-ac00-45ae-849a-58dbd2140916

https://crash-stats.mozilla.com/report/index/31608b3a-1436-4097-aa85-97f102140916

https://crash-stats.mozilla.com/report/index/cf154fc9-b627-46c1-884c-155ae2140916


Expected results:

Firefox should close without issues

Updated

4 years ago
Crash Signature: [@ xul.dll@0xefbe6c | xul.dll@0x86289 | xul.dll@0xefc734 | xul.dll@0xbb335 | xul.dll@0xee3cd4 | xul.dll@0xefbe37 | xul.dll@0xe840a5 | xul.dll@0xe7b415 | xul.dll@0xe83e67 | xul.dll@0xa9e56 | mozglue.dll@0xfedc ]
Keywords: crash
The crash IDs are unusable because the symbols are missing :-(
(Reporter)

Comment 2

4 years ago
(In reply to Matthias Versen [:Matti] from comment #1)
> The crash IDs are unusable because the symbols are missing :-(

What can i do to fix this, do you need the Crash ID's from about:crashes? if so, here they are:
bp-cf0af414-d351-47d8-83c8-0bc3b2140916	16-9-2014	21:12
bp-7ba807ab-8f30-4ba4-945b-624cb2140916	16-9-2014	21:00
bp-ca40417f-ac00-45ae-849a-58dbd2140916	16-9-2014	20:29
bp-31608b3a-1436-4097-aa85-97f102140916	16-9-2014	20:28
bp-cf154fc9-b627-46c1-884c-155ae2140916	16-9-2014	20:09
bp-f7b7b0bf-5dde-4963-9ae2-c42ba2140916	16-9-2014	20:02
bp-9b615a33-6594-4c9e-ae98-cb9b22140916	16-9-2014	19:39
>What can i do to fix this, do you need the Crash ID's from about:crashes?
Are you using "official" builds from mozilla.org ?
The crash server only knows the symbols for official builds but it can be that there is some other kind of problem with the crash server
(Reporter)

Comment 4

4 years ago
(In reply to Matthias Versen [:Matti] from comment #3)
> >What can i do to fix this, do you need the Crash ID's from about:crashes?
> Are you using "official" builds from mozilla.org ?
> The crash server only knows the symbols for official builds but it can be
> that there is some other kind of problem with the crash server

I don't think its the crash server, i  compile my own builds, the difference being that i optimized it for 'core-avx-i'and i've disabled the updater and maintenance service.

Since there isn't any way to diagnose te problem should the bug / ticket be closed?
Ah, you are using your own builds !
The crash server needs the debug symbols from the build machine. The Mozilla build systems upload the debug symbols for each build on the Mozilla crash server. In case of an incoming crash report the debug symbols and the crash signature are linked together and you get a useful stacktrace with debug symbols.

You have only 2 options : Build a slow debug build or compile an optimized build with symbols and then use the debugger.
A third option would be to reproduce the crash with a Mozilla.org binary.

I will mark this bug report incomplete because there is nothing that we can do here
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INCOMPLETE
(Reporter)

Comment 6

4 years ago
(In reply to Matthias Versen [:Matti] from comment #5)
> Ah, you are using your own builds !
> The crash server needs the debug symbols from the build machine. The Mozilla
> build systems upload the debug symbols for each build on the Mozilla crash
> server. In case of an incoming crash report the debug symbols and the crash
> signature are linked together and you get a useful stacktrace with debug
> symbols.
> 
> You have only 2 options : Build a slow debug build or compile an optimized
> build with symbols and then use the debugger.
> A third option would be to reproduce the crash with a Mozilla.org binary.
> 
> I will mark this bug report incomplete because there is nothing that we can
> do here

Alright then thank you for you're effort!
You need to log in before you can comment on or make changes to this bug.