545090 - improve crash reporter

Status: RESOLVED DUPLICATE of bug 429592

(Toolkit :: Crash Reporting, defect)

Description

[Black_Ps`]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6

I have seen i don't know how many times firefox crashing without any report submitting , i was just searching in pages in google and the browser crashed, This addon    Crash Report Helper 1.2  ( https://addons.mozilla.org/en-US/firefox/addon/11217 ) can detect when it's a force quit and crash report can't ? this is a disaster ..can you please check the problem out.


Thanks..

Reproducible: Always

Comment 1

[Jo Hermans]

What makes you think that it will help you identifying more crashes ? This only improves the reports that were sent by the crash reporter (so it must have been reported before). Very useful I agree, but not for the reason you want.

Comment 2

[Black_Ps`]

The motive of this is not me,and all the people that use firefox and when it crash if they don't submit a crash report what is the reason of crashreporter.exe in mozilla then if it's not working very good and can't tell when the mozilla has been forced to close or a crash ?

Comment 3

[Tyler Downer [He/Him]]

So, basically uplift the crash reporter helper extension you mean?

Comment 4

[Black_Ps`]

What i mean is that the crashreporter must be improved to submit all the crashes,as there is a big problem with it,i don't know how many crashes i had without any report..i think this is bad,very bad..

Thanks.

Comment 5

[(not currently active) Ted Mielczarek]

What does Crash Report Helper do that you think the crash reporter should be doing? I'm sorry, it's not clear to me exactly what you're requesting. When you say "can detect when it's a force quit", what does it do?

Comment 6

[Black_Ps`]

"can detect when it's a force quit" I mean if the browser crashes or if you close it and it crashes ,when you start firefox ,Crash Report Helper can tell that the browser had a crash or a forced quit ,crashreporter did not submit anything this is what i mean,i mean a improvement in crashreporter to detect all crashes. Like Crash Report Helper,For example if you close firefox with ctrl+alt+delete from taskmanager, i don't think crash reporter can detect it,but  Crash Report Helper will tell you that your browser had a forced quit without any crash reporter submited. I hope you can understand what i mean.

Comment 7

[(not currently active) Ted Mielczarek]

Ok, thanks for clarifying. We could do something similar in Firefox to detect that issue. However, it wouldn't actually do us any good. Just knowing that the user killed the process doesn't tell us anything. Getting a crash report gives us information about exactly what the process was doing at the time of the crash, which we can use to fix the root cause. Just knowing that the application was hung or forcibly killed gives us no data to fix it. We do have bug 429592 on file about detecting that the process is hung and submitting a crash report on that. Would that cover your use case here?

Comment 8

[Black_Ps`]

Yes it's great,the one with the kill from taskmanager was just an example,i know that will not help,this bug is just one of the 3 problems,if the browser crash without a report you can't restore the window as firefox thinks he had been closed,second that it's not detecting all crashes,and the last is this yes  bug 429592 ,a about:restore must be implanted if the browser crashes without any report you can't restore windows...bad

Comment 9

[(not currently active) Ted Mielczarek]

about:sessionrestore should work just fine if you forcibly kill the process. It doesn't have any dependency on crash reporting.

Comment 10

[Black_Ps`]

oh ok..

Comment 11

[(not currently active) Ted Mielczarek]

I'm going to resolve this as a duplicate of bug 429592, since I think that fixing that bug would fix your biggest issue. We don't really like to have multiple issues mixed into a single bug, so if you're seeing problems where you're not getting about:sessionrestore when killing a process, could you please file a separate bug on that? (If you have a set of steps that you can reproduce the problem with, that will make it a lot easier to understand.)