Bug 1279293 (IPCError_ShutDownKill)

[meta] Crash in [@ IPCError-browser | ShutDownKill]

NEW
Unassigned

Status

()

P2
critical
3 years ago
a month ago

People

(Reporter: marvinhk, Unassigned)

Tracking

(Depends on: 22 bugs, Blocks: 1 bug, 6 keywords)

38 Branch
crash, crashreportid, meta, multiprocess, qawanted, topcrash
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox47 wontfix, firefox48 wontfix, firefox49 wontfix, firefox-esr45 wontfix, firefox50+ wontfix, firefox51 wontfix, firefox52 wontfix, firefox-esr52 wontfix, firefox53 wontfix, firefox54 affected, firefox55 affected, firefox56 affected, firefox57 affected, firefox58 affected, firefox59 affected, firefox60 affected, firefox61 affected)

Details

(crash signature, URL)

(Reporter)

Description

3 years ago
This bug was filed from the Socorro interface and is 
report bp-3bbe367b-ff88-4040-90de-0567a2160609.
=============================================================
new signature in JSStructuredCloneWriter

Comment 1

2 years ago
I had a huge FF session in SafeMode and by exit got this crash, too: https://crash-stats.mozilla.com/report/index/d0758d13-d0c8-4ccf-985b-bf1522160615
This link seems to freeze browser and I just got a 'shut down' kill' crash.

https://crash-stats.mozilla.com/report/index/cfd92e66-a5e1-44be-b18d-33b982160625

Running Win10 x64 and Win32 Nighly builds.
 	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
e10s in 'enabled'  Same, goes not responding with e10s 'off'

No idea when this started, just noticed today trying to visit:
http://www.mayoclinic.org/diseases-conditions/retrograde-ejaculation/basics/definition/con-20030795
Status: UNCONFIRMED → NEW
Ever confirmed: true
Just discovered that it does not Hang with 'Tracking Protection' 'OFF' 

Options->Privacy:  Had it set to 'Always',  Flipping to 'Never' stops the hang.
This signature covers a lot of possible issues. It looks like we don't have a bug on it, so this can be the one.

Jim, I filed bug 1282580 for the issue you're seeing. The shutdown hang is really a side effect of a different problem (that the site is hanging).
See Also: → bug 1282580
20160629030209 Mozilla/5.0 (Windows NT 6.1; rv:50.0) Gecko/20100101 Firefox/50.0

Nightly 50.0a1 crashed having the same signature as the one from this bug with the following steps:

1. Load http://html.spec.whatwg.org/
2. Press Ctrl+F to open the Find toolbar
3. Scroll the page up and down
4. Close FF

Expected results:
The page should be loaded without crashing


Actual results:
The page is loaded, Find toolbar is not opened,the page is not scrolled and after page is closed Firefox crashes: 
https://crash-stats.mozilla.com/report/index/e013a326-36b4-4cad-829c-8efc42160630
This is a generic signature, so different steps to cause a crash from this signature should have separate bugs, blocking this bug.
We'll need a multifaceted approach here. Comment 5 isn't really even a bug, exactly. If a web page is doing a lot of work and you quit, then the content process is going to be slow to respond (slower than 5 seconds). It's probably reasonable to increase the timeout to 30 seconds.
Priority: -- → P2

Comment 8

2 years ago
I thought the plan here was to get rid of this entirely by just killing the content process when we didn't need it any more. We cannot afford to let content block shutdown for significant periods of time (5 seconds is already too much in general).

Comment 9

2 years ago
Can I ask something?

I have a lots of tabs, so most of the time e.g. last year closing/restarting FireFox took forever (sometimes literally since you would just never see the damn thing going away from the task manager process list no matter for how long you wait), but in recent months there was a change that has finally put a time limit on how long FF can stay in the memory after you commanded exit. Though it is still takes unacceptably long time.

Correct me if I am wrong, but from what I understand, there were no fundamental changes in how FF operates, but what was done was literally implementation of a time limit after which FireFox/PluginContainer gets killed no matter what. As result, ever since that change, absolutely every exit/restart I have in FF ends with a crash like this one or of another type of ShutDownKill. 

Can some please explain why it is impossible to redesign things in a way that would allow FireFox exit/restart ***right away***? Or maybe such development project is already ongoing within Mozilla quarters, and it is supposed to "land" in FF version 55 or something?

Thanks in advance.
(In reply to Benjamin Smedberg  [:bsmedberg] from comment #8)
> I thought the plan here was to get rid of this entirely by just killing the
> content process when we didn't need it any more. We cannot afford to let
> content block shutdown for significant periods of time (5 seconds is already
> too much in general).

The problem I realized only recently is with "beforeunload", "unload", and "pagehide" events. Currently, Firefox fires them on shutdown. They can do sync XHRs, so they have observable side effects. Sync XHRs are "deprecated" (although no one seems very hopeful that we'll ever be able to remove them), but the beacon API is new and we would need to support that at shutdown as well (currently I'm not sure if that even works).

If we stop firing this stuff at shutdown, we're probably going to break a lot of websites. There's a github issue on the topic [1] that links to a bunch of Chrome usage counters, and it seems like a lot of sites are using sync XHR in unload (something like 0.3% of web pages as far as I understand the data).

I think we could probably make an effort to fire these event listeners but not do any of the other teardown activities associated with destroying a docshell. That might save us a good amount of time.

[1] https://github.com/whatwg/xhr/issues/20#issuecomment-185163375
Setting needinfo to Benjamin in case you have an opinion or ideas on comment 10.
Flags: needinfo?(benjamin)

Comment 12

2 years ago
I assumed that shutdown worked like this (and I'm totally terrible for assuming this):

* the Firefox UI code knows that we're quitting.
** It triggers beforeunload handlers before we've actually decided to quit, so that we can support the returnValue/confirmation UI.
** Then we trigger the unload (and pagehide?) events as part of closing the Firefox window
** This process also collects any final session restore information
* Only after we're finished shutting down the user-visible bits do we trigger the content process to quit
** At this point, the content process shouldn't contain any important user data and in non-leakchecking builds we can just kill it (using TerminateProcess/SIGTERM)
** In leakchecking builds we'd do the full/painful shutdown sequence

So you're saying that we don't trigger some of the unload events until we've actually told the content process to quit? That seems like it might be both a UI regression (in case the beforeunload event has quit confirmation prompts) and might cause weird teardown sequence errors in the Firefox UI.
Flags: needinfo?(benjamin) → needinfo?(wmccloskey)
Your description is correct as I understand things, except maybe for when we start the shutdown timer.

A typical sequence is:
1. We run "beforeunload" events before everything else.

2. Parent does session restore, which does spin the event loop waiting for the child. But at this point nothing has been closed and this is pretty fast.

3. Parent closes all the windows, which closes all tabs, which causes an async message to be sent to the child asking it to tear down the docshell for that tab. Destroying a docshell fires "unload"/"pagehide" and also frees memory for the tab (DOM, frame tree, etc.).

4. Parent ends up in ContentParent::Observe("xpcom-shutdown"), at which time it asks the child to shut down. If the child fails to shut down after 5 seconds, it kills it.

We could introduce more waiting to give the child a chance to finish running its "unload"/"pagehide"/docshell destruction code before we start the 5 second timer in step (4). However, that would defeat the purpose of the timer, since AFAIK step (3) is what takes all the time. When you have 20 tabs and we have to free the memory for all of them as well as handle any sync network requests they make, it can easily take > 5 seconds.

To put it another way, once all the docshells are gone, shutting down the content process is trivial (in opt builds). There's a little bit of message traffic with the parent, but basically the child just calls QuickExit.

If we want to save time here, I think the best we can do is avoid freeing the DOM/frame tree/whatever else. I'd be interested in how other browsers handle this. I Googled for "firefox shutdown slow" and "chrome shutdown slow". There are a lot more results for Firefox.
Flags: needinfo?(wmccloskey)
Tracking this for 50, seems like a high volume crash good to keep an eye on.
status-firefox50: --- → affected
tracking-firefox50: --- → +

Comment 15

2 years ago
>  However, that would defeat the purpose of the timer, since AFAIK step (3) is what takes all the time.

How about tearing down tabs 1 by 1 and giving each one a separate timeout. That way a hang can still be detected by the timeout scales with the tabs.
Crash volume for signature 'IPCError-browser | ShutDownKill':
  - aurora (49): 69120
  - beta (48): 805
  - release (47): 702
  - esr (45): 14

Affected platforms: Windows, Mac OS X, Linux
status-firefox47: --- → affected
status-firefox48: --- → affected
status-firefox49: --- → affected
status-firefox-esr45: --- → affected
(In reply to Bill McCloskey (:billm) from comment #13)

> If we want to save time here, I think the best we can do is avoid freeing
> the DOM/frame tree/whatever else. I'd be interested in how other browsers
> handle this. I Googled for "firefox shutdown slow" and "chrome shutdown
> slow". There are a lot more results for Firefox.

Andrew do you know who might be able chase this?
Flags: needinfo?(overholt)

Comment 18

2 years ago
Would the idea with this be to, instead of closing all of the windows, trigger the firing of these "beforeunload", doing SessionStore stuff, "unload", and "pagehide" etc. events, and then just kill the child process outright, without performing any of the usual cleanup? (I presume that the child process would QuickExit() itself)
Flags: needinfo?(wmccloskey)
(In reply to Michael Layzell [:mystor] from comment #18)
> Would the idea with this be to, instead of closing all of the windows,
> trigger the firing of these "beforeunload", doing SessionStore stuff,
> "unload", and "pagehide" etc. events, and then just kill the child process
> outright, without performing any of the usual cleanup? (I presume that the
> child process would QuickExit() itself)

Yes. We already avoid application-level cleanup (e.g., XPCOM shutdown) by calling QuickExit. We additionally would like to avoid any docshell-level cleanup we're doing now. Probably the first step, though, is to see how expensive that cleanup is.
Flags: needinfo?(wmccloskey)
Flags: needinfo?(overholt)

Comment 20

2 years ago
¡Hola!

Just crashed like this on Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0 ID:20160831030224 CSet: 506facea63169a29e04eb140663da1730052db64

Report ID 	Date Submitted
bp-5141c955-afeb-4668-ac9f-c4dcb2160831
	31/08/2016	09:31 a.m.

https://crash-stats.mozilla.com/signature/?product=Firefox&signature=IPCError-browser%20%7C%20ShutDownKill says there were 35318 in the past week so this one seems to be popular.

¡Gracias!
Alex
status-firefox51: --- → affected
After a normal Nightly update, I got a "you have unsubmitted crash reports" infobar. After submitting, I went to about:crashes and saw that it was a crash with this signature (https://crash-stats.mozilla.com/report/index/e9600c03-5f4c-47a8-b33f-39ee72160831). Since the "crash" wasn't actually user-visible in any way, it probably falls under the "not a real bug" scenario, and it was only made evident to me by the existence of the infobar. I've gotten that same infobar a number of times in the last month after updating Nightly, so it wouldn't surprise me if a lot of the crashes reported with this signature are also not otherwise user-visible.
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #21)
> After a normal Nightly update, I got a "you have unsubmitted crash reports"
> infobar. After submitting, I went to about:crashes and saw that it was a
> crash with this signature
> (https://crash-stats.mozilla.com/report/index/e9600c03-5f4c-47a8-b33f-
> 39ee72160831). Since the "crash" wasn't actually user-visible in any way, it
> probably falls under the "not a real bug" scenario, and it was only made
> evident to me by the existence of the infobar. I've gotten that same infobar
> a number of times in the last month after updating Nightly, so it wouldn't
> surprise me if a lot of the crashes reported with this signature are also
> not otherwise user-visible.

Yes, I also get the crash report bar for this signature after updating Nightly.  I believe I see it for every Nightly update.

Comment 23

2 years ago
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #21)
> Since the "crash" wasn't actually user-visible in any way, it
> probably falls under the "not a real bug" scenario, and it was only made
> evident to me by the existence of the infobar.

It might be a real bug because my YouTube tabs can never remember the time when the playback was stopped before Firefox was closed/restarted -- as FF can never finish the process properly, it always crashes. It is super annoying, and for more than half of a year nothing gets fixed. :(

https://crash-stats.mozilla.com/report/index/1ee465ba-fc81-417c-9bc2-8c4852160831

Could
Flags: needinfo?(bugmail)

Comment 24

2 years ago
I literally see it every time I restart my Nightly. 
As Kartikaya said, I never saw it, except for the constant reminders about having unsubmitted crash reports. 

I've set dom.ipc.tabs.shutdownTimeoutSecs to 30 seconds for now and I don't get those crash reports anymore. I've probably submitted around 200 reports at this point.

Comment 25

2 years ago
I just wanted to ask if it is possible to have an approximate timeline when those FF crashes during exit will go away. Maybe solving this will take a quarter or two, and maybe some one will be assigned to this bug? Thank you in advance.
Flags: needinfo?(bugmail)
status-firefox47: affected → wontfix
status-firefox48: affected → wontfix

Updated

2 years ago
Duplicate of this bug: 1287702

Updated

2 years ago
Duplicate of this bug: 1299781
IMO if the content process is blocked by the event handler of unload or pagehide, we should not treat them as shutdown hang. We should think of a way to let the script finish or set a timeout if the sync API is called in such event handlers.
I think there are maybe 36% content shutdown hang kill bugs are from the nested-event-loop handling. I'm not sure but I want to add some annotations in ContentChild to measure this.
Component: IPC → DOM: Content Processes
Depends on: 1301339
Depends on: 1301346

Updated

2 years ago
See Also: → bug 1301464
Duplicate of this bug: 1286053
I'm thinking we should start here by increasing the timeout a little bit. I looked through the crash reports today and didn't see too many patterns. We may have a problem with sync messages to the parent that aren't being handled, but it's not certain that that's what's happening.
Based on the patch Kan-Ru added in bug 1301339, out of 5763 ShutDownKill crashes in the last week, we received the Shutdown message in 278 of them (and sent FinishShutdown in 1).

So in most cases we never even get a chance to receive the Shutdown message.
(In reply to Bill McCloskey (:billm) from comment #34)
> Based on the patch Kan-Ru added in bug 1301339, out of 5763 ShutDownKill
> crashes in the last week, we received the Shutdown message in 278 of them
> (and sent FinishShutdown in 1).
> 
> So in most cases we never even get a chance to receive the Shutdown message.

That's terrible. Maybe shutdown message should not use PContent. It can use PBackground and preempt the current task on content main thread.
(In reply to Kan-Ru Chen [:kanru] (UTC+8) from comment #35)
> (In reply to Bill McCloskey (:billm) from comment #34)
> > Based on the patch Kan-Ru added in bug 1301339, out of 5763 ShutDownKill
> > crashes in the last week, we received the Shutdown message in 278 of them
> > (and sent FinishShutdown in 1).
> > 
> > So in most cases we never even get a chance to receive the Shutdown message.
> 
> That's terrible. Maybe shutdown message should not use PContent. It can use
> PBackground and preempt the current task on content main thread.

The problem is that we're really supposed to run onunload handlers before we shut down, and I suspect that might be what's taking so long.
Kan-Ru & :billm
This volume of the crashes is getting worse in 51 aurora. I this the priority should be adjusted to P1. Can you help to investigate this more?
Flags: needinfo?(wmccloskey)
Flags: needinfo?(kchen)
Priority: P2 → P1
bug 1301346 should get us more insight about onunload handler behavior.
Flags: needinfo?(kchen)
Flags: needinfo?(wmccloskey)
This signature got a lot worse (from 7 crashes a day to 5000 crashes a day) on October 20th. 
Maybe we can find a regression range. Can the uptime team help?
Flags: needinfo?(n.nethercote)
(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #39)
> This signature got a lot worse (from 7 crashes a day to 5000 crashes a day)
> on October 20th. 
> Maybe we can find a regression range. Can the uptime team help?

Looking at the Windows builds at https://dbaron.org/mozilla/crashes-by-build...

- Oct 18: 119
- Oct 19: 172
- Oct 20: 1317
- Oct 21: 35 (*)
- Oct 22: 889

(*) Ignore this one because the internet was mostly broken that day due to the Dyn DDoS issues and very few users got an updated Nightly. This probably also means that the Oct 20 number is inflated.

Judging from this the number of daily crashes went from ~100 to ~1000. Still not good, but not quite as bad as 7 to 5000.

I then used the regression window tool at https://dbaron.org/mozilla/crashes-by-build (click on the "Choose regression window" button, then select the Oct 19 and Oct 20 Windows builds) and got this regression range:

https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=90d8afaddf9150853b0b68b35b30c1e54a8683e7&tochange=99a239e1866a57f987b08dad796528e4ea30e622

A couple of wild guesses about changes that might have caused this:

* Valentin Gosu — Bug 1294719 - Make sure to check mIPCClosed before calling SendRedirect1Begin r=honzab 
* Aaron Klotz — Bug 1241921: Disable async plugin init regardless of pref; r=jimm 

Valentin, Aaron, could either of these changes have caused the number of crashes with this signature to have increased by ~10x?
If anyone else could look through the regression list, that would be helpful too.
Flags: needinfo?(valentin.gosu)
Flags: needinfo?(n.nethercote)
Flags: needinfo?(aklotz)
(In reply to Nicholas Nethercote [:njn] from comment #40)
> * Aaron Klotz — Bug 1241921: Disable async plugin init regardless of pref;
> r=jimm 

My change could not have done that, as that feature was already disabled by pref. That patch simply hardcoded it.

That merge also included the enabling of a11y+e10s on Windows Vista and newer, but I took the liberty of checking the aggregations for that. Only 5% of Windows crashes since October 20 had a11y turned on.
Flags: needinfo?(aklotz)
Also if this change
68956648f506	Aaron Klotz — Bug 1241921: Remove CreateWindow* hooks from IPC glue; r=jimm
were to cause any problems, they would typically be a spike in stack overflow crashes, which is not what we're seeing here. I'm ruling that one out too.

Comment 43

2 years ago
Drop in crashes between 12th and 21st is possibly from Socorro updates.
From the crash stat report https://goo.gl/VRclPs, there is a big spike in content crashes on Oct 20. From the pushlog between Oct 19 and Oct 20 on aurora branch - https://hg.mozilla.org/releases/mozilla-aurora/pushloghtml?startdate=2016-10-19&enddate=2016-10-20, there are coupe of fixes landed in aurora.

Just a guess, the fix of bug 1308397 & bug 1304449 might have something to do with this spike.

:aklotz, can you help take a look at this?
Flags: needinfo?(aklotz)
(In reply to Nicholas Nethercote [:njn] from comment #40)
> * Valentin Gosu — Bug 1294719 - Make sure to check mIPCClosed before calling
> SendRedirect1Begin r=honzab 
> could these changes have caused the number of
> crashes with this signature to have increased by ~10x?

It is possible that some of the crashes in bug 1294719 could have transformed to this one. It would be easy to find out by backing out that patch since it didn't fix the issue. However, based on comment 44 I understand the crash spike also affected aurora. That patch didn't get uplifted.
Flags: needinfo?(valentin.gosu)
This doesn't seem to be worse on beta50 than previous releases, and it's getting late in the cycle, wontfix.
status-firefox50: affected → wontfix
(In reply to Gerry Chang [:gchang] from comment #44)
> From the crash stat report https://goo.gl/VRclPs, there is a big spike in
> content crashes on Oct 20. From the pushlog between Oct 19 and Oct 20 on
> aurora branch -
> https://hg.mozilla.org/releases/mozilla-aurora/pushloghtml?startdate=2016-10-
> 19&enddate=2016-10-20, there are coupe of fixes landed in aurora.
> 
> Just a guess, the fix of bug 1308397 & bug 1304449 might have something to
> do with this spike.
> 
> :aklotz, can you help take a look at this?

Once again, most of those crashes happen with a11y off. Also, if you isolate this signature to Mac OS X, you see a similar spike. I maintain that something else is causing this.
Flags: needinfo?(aklotz)
Also those two patches landed on Nightly on Oct 6 and 18, respectively.
There was a spike in both Nightly and Aurora between the Oct 19 and the Oct 20 builds.

The only bugs that landed on Oct 19 in both Nightly and Aurora are bug 1305993 and bug 1309198.
Flags: needinfo?(jonathan)

Comment 51

2 years ago
The period I list is from;
https://crash-analysis.mozilla.com/rkaiser/crash-report-tools/longtermgraph/?fxaurora
Which also has a loss of plugin hangs for the period.

You or someone with knowledge of Socorro would have to pinpoint possible change. Just reading commit messages; nothing sticks out to me (don't know the code) to end the loss, bug 1306449 possibly start.
Flags: needinfo?(jonathan)
Do you know if something happened that would cause this crash to almost disappear between Oct 12 and Oct 21?
Flags: needinfo?(peterbe)
Flags: needinfo?(adrian)
(In reply to Marco Castelluccio [:marco] from comment #52)
> Do you know if something happened that would cause this crash to almost
> disappear between Oct 12 and Oct 21?

Most likely it's because of a bug in the processor. 
It was introduced in https://github.com/mozilla/socorro/commit/1e180913c464bdfc77602fc26a9cb8bea0c47712 (deployed on Oct 12)
And later fixed in https://github.com/mozilla/socorro/commit/c049e63f6bdd0e29acadbe326a68d9890fcd67f0 (deployed on Oct 21)

The original bug that found this was: https://bugzilla.mozilla.org/show_bug.cgi?id=1311697
Ludovic noticed it by simply trying to load a crash.
Here was a crash that just never succeeded in the processor. We debugged it and found the problem and after deploying that particular crash could be processed again. 

We thought this was a unique snowflake because it didn't appear to impact the general numbers. (Or we just didn't look at the right range when comparing to previous days)

By the way, this was my first processor bug that I had to work on and to avoid this happening in the future we just landed Sentry error handling in the processor. Prior to that, the only way we could find out that certain crashes fail and drop on the floor was if people ssh into the processor nodes and look at the logs. 

Marco, do you want to start a reprocessing of this date range? If so, talk to me about doing it "gently" and I'll talk to JP about scaling up the infra.
Flags: needinfo?(peterbe)
Flags: needinfo?(adrian)

Updated

2 years ago
Duplicate of this bug: 1321449
Are you able to reproduce this crash consistently? Do you have steps to reproduce?
Flags: needinfo?(condacum)

Comment 59

2 years ago
After installing FF50 (ok with previous builds), I have this silent crash every day, i.e. when I close firefox at the end of the day.

Updated

2 years ago
Flags: needinfo?(condacum)

Comment 60

2 years ago
silent crash because the day after I notice the crash of the day before and so on...never notice before ff50.

Comment 61

2 years ago
(In reply to Marco Castelluccio [:marco] from comment #58)
> Are you able to reproduce this crash consistently? Do you have steps to
> reproduce?

:marco You didn't ask me, but I continue to have several of these crashes each day. For example, Nightly updates itself about mid-morning for me. about:crashes shows me that every updates brings a silent crash, e.g. https://crash-stats.mozilla.com/report/index/cf2a5f92-14da-4e1d-a052-f667a2161217.
I'm not sure if this is of any help, but I've managed to reproduce this crash pretty consistently with the latest m-c [1] using the following STR:

* install the latest version of m-c
* set "When nightly starts: Show my window and tabs from last time" under about:preferences#general
* opened several tabs/websites in several different custom containers (http://imgur.com/a/zMh60)
* closed/restarted fx several times

I noticed that the crash started occurring when I tried opening m-c while it was attempting to shutdown initially. After that, I started getting the crash with every fx restart.

Crashes:

* bp-ff8ee990-5b23-43c3-a3e8-4e48e2161219
* bp-1146cec8-6ed7-42cf-9571-67f872161219
* bp-1384ea42-7d95-46f8-be8b-a3d5e2161219
* bp-e296be83-7fa1-4ede-afb0-455cb2161219

[1] fx53.0a1, buildid: 20161219030207, changeset: 863c2b61bd27
I've managed to narrow down the STR from comment#62 to the following:

* install the latest version of m-c
* open https://twitter.com/i/moments/810878086774456320
* let one of the random gifs start autoplaying and quickly shutdown FX

You'll notice that the shutdown process will hang and will take several seconds for fx to correctly close.

I've created a quick video of the STR that I used to reproduce the crash on a brand new m-c installation under macOS 10.12.2:
* https://youtu.be/SQ6x5iWVaqg
(In reply to Kamil Jozwiak [:kjozwiak] from comment #63)
> I've managed to narrow down the STR from comment#62 to the following:
> 
> * install the latest version of m-c
> * open https://twitter.com/i/moments/810878086774456320
> * let one of the random gifs start autoplaying and quickly shutdown FX
> 
> You'll notice that the shutdown process will hang and will take several
> seconds for fx to correctly close.
> 
> I've created a quick video of the STR that I used to reproduce the crash on
> a brand new m-c installation under macOS 10.12.2:
> * https://youtu.be/SQ6x5iWVaqg

Can you file a new bug for this (be sure to also attach a link to a crash report)?
(In reply to Marco Castelluccio [:marco] from comment #64) 
> Can you file a new bug for this (be sure to also attach a link to a crash
> report)?

Sure :) Created bug#1324820. Let me know if there's anything else that I can help out with.
Comment hidden (spam)
Comment hidden (spam)
Comment hidden (spam)
Depends on: 1346161
Could you describe your environment with more details? For example how many tabs were opened when you were closing Firefox? Can you reproduce it with addons disabled? It will help us understand the issue and increase the possibility of getting this fixed. It will help if you have clear steps to reproduce the issue.

You can also attach the content from about:support page here or mail it to me directly.
Flags: needinfo?(condacum)

Comment 73

2 years ago
10 tabs. 
yes.


Informazioni di base
--------------------

Nome: Firefox
Versione: 52.0
ID build: 20170302120751
Canale di aggiornamento: release
User agent: Mozilla/5.0 (Windows NT 6.0; rv:52.0) Gecko/20100101 Firefox/52.0
SO: Windows_NT 6.0
Finestre multiprocesso: 2/2 (Attivato automaticamente)
Modalità provvisoria: false

Segnalazioni di arresto anomalo degli ultimi 3 giorni
-----------------------------------------------------

Tutte le segnalazioni di arresto anomalo (incluse 3 in attesa nell’intervallo di tempo indicato)

Estensioni
----------

Nome: Adblock Plus
Versione: 2.8.2
Attiva: true
ID: {d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}

Nome: Application Update Service Helper
Versione: 2.0
Attiva: true
ID: aushelper@mozilla.org

Nome: Multi-process staged rollout
Versione: 1.9
Attiva: true
ID: e10srollout@mozilla.org

Nome: NoScript
Versione: 5.0.1
Attiva: true
ID: {73a6fe31-595d-460b-a920-fcc0f8843232}

Nome: Pocket
Versione: 1.0.5
Attiva: true
ID: firefox@getpocket.com

Nome: Web Compat
Versione: 1.0
Attiva: true
ID: webcompat@mozilla.org

Grafica
-------

Caratteristiche
Composizione: Direct3D 11
Panoramica/zoom asincroni (APZ): input rotella attivo; input touch attivo
Rendering WebGL: Google Inc. -- ANGLE (NVIDIA GeForce GTX 650 Direct3D11 vs_5_0 ps_5_0)
Rendering WebGL2: Google Inc. -- ANGLE (NVIDIA GeForce GTX 650 Direct3D11 vs_5_0 ps_5_0)
Decodifica hardware H264: No; Hardware video decoding disabled or blacklisted
Back-end audio: wasapi
DirectWrite: false (7.0.6002.24017)
GPU #1
Attivo: Sì
Descrizione: NVIDIA GeForce GTX 650
ID produttore: 0x10de
ID dispositivo: 0x0fc6
Versione driver: 9.18.13.4788
Data aggiornamento driver: 3-13-2015
Driver: nvd3dum,nvwgf2um,nvwgf2um
ID sottosistema: 00000000
RAM: 2048

Diagnostica
AzureCanvasAccelerated: 0
AzureCanvasBackend: skia
AzureContentBackend: skia
AzureFallbackCanvasBackend: cairo
Registro decisioni
D3D9_COMPOSITING:
disabled by default: Disabled by default
DIRECT2D:
unavailable by runtime: Failed to acquire a Direct2D 1.1 factory




Preferenze importanti modificate
--------------------------------

accessibility.typeaheadfind.flashBar: 0
browser.cache.disk.capacity: 358400
browser.cache.disk.filesystem_reported: 1
browser.cache.disk.smart_size_cached_value: 358400
browser.cache.disk.smart_size.first_run: false
browser.cache.disk.smart_size.use_old_max: false
browser.cache.frecency_experiment: 1
browser.display.focus_ring_on_anything: true
browser.download.folderList: 0
browser.download.importedFromSqlite: true
browser.download.manager.alertOnEXEOpen: true
browser.download.manager.closeWhenDone: true
browser.download.manager.quitBehavior: 2
browser.download.manager.retention: 0
browser.download.manager.scanWhenDone: false
browser.link.open_newwindow: 2
browser.places.importBookmarksHTML: false
browser.places.importDefaults: false
browser.places.leftPaneFolderId: -1
browser.places.migratePostDataAnnotations: false
browser.places.smartBookmarksVersion: 8
browser.places.updateRecentTagsUri: false
browser.search.suggest.enabled: false
browser.search.update: false
browser.sessionstore.max_tabs_undo: 45
browser.sessionstore.restore_on_demand: false
browser.sessionstore.upgradeBackup.latestBuildID: 20170302120751
browser.startup.homepage: https://startpage.com/
browser.startup.homepage_override.buildID: 20170302120751
browser.startup.homepage_override.mstone: 52.0
browser.tabs.drawInTitlebar: false
browser.tabs.onTop: false
browser.tabs.remote.autostart.2: true
browser.urlbar.formatting.enabled: false
browser.urlbar.trimURLs: false
dom.apps.lastUpdate.buildID: 20161019084923
dom.apps.lastUpdate.mstone: 49.0.2
dom.apps.reset-permissions: true
dom.disable_window_move_resize: true
dom.event.clipboardevents.enabled: false
dom.ipc.plugins.timeoutSecs: -1
dom.max_chrome_script_run_time: 40
dom.max_script_run_time: 40
dom.mozApps.used: true
dom.w3c_touch_events.expose: false
extensions.lastAppVersion: 52.0
font.internaluseonly.changed: true
gfx.crash-guard.d3d11layers.appVersion: 52.0
gfx.crash-guard.d3d11layers.deviceID: 0x0fc6
gfx.crash-guard.d3d11layers.driverVersion: 9.18.13.4788
gfx.crash-guard.d3d11layers.feature-d2d: true
gfx.crash-guard.d3d11layers.feature-d3d11: true
gfx.crash-guard.glcontext.gfx.driver-init.direct3d11-angle: true
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle: true
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-d3d11: false
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-warp: false
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-try-d3d11: true
gfx.crash-guard.status.d3d11layers: 2
gfx.crash-guard.status.d3d9video: 2
gfx.crash-guard.status.glcontext: 2
gfx.direct3d.checkDX10: true
gfx.direct3d.last_used_feature_level_idx: 0
gfx.direct3d.prefer_10_1: true
gfx.driver-init.appVersion: 42.0
gfx.driver-init.deviceID: 0x0fc6
gfx.driver-init.driverVersion: 9.18.13.4788
gfx.driver-init.feature-d2d: true
gfx.driver-init.feature-d3d11: true
gfx.driver-init.status: 2
layers.offmainthreadcomposition.enabled: false
media.encoder.webm.enabled: false
media.gmp-eme-adobe.abi: x86-msvc-x86
media.gmp-eme-adobe.enabled: false
media.gmp-eme-adobe.lastUpdate: 1461675179
media.gmp-eme-adobe.version: 17
media.gmp-gmpopenh264.abi: x86-msvc-x86
media.gmp-gmpopenh264.lastUpdate: 1473678394
media.gmp-gmpopenh264.version: 1.6
media.gmp-manager.buildID: 20170302120751
media.gmp-manager.lastCheck: 1489402453
media.gmp-widevinecdm.abi: x86-msvc-x86
media.gmp-widevinecdm.enabled: false
media.gmp-widevinecdm.lastUpdate: 1474362385
media.gmp-widevinecdm.version: 1.4.8.903
media.gmp.storage.version.observed: 1
media.hardware-video-decoding.failed: true
media.mp4.enabled: false
media.webm.enabled: false
media.webrtc.debug.aec_log_dir: C:\Users\admin\AppData\Local\Temp
media.webrtc.debug.log_file: C:\Users\admin\AppData\Local\Temp\WebRTC.log
network.cookie.cookieBehavior: 1
network.cookie.lifetimePolicy: 2
network.cookie.prefsMigrated: true
network.dns.disableIPv6: true
network.predictor.cleaned-up: true
places.database.lastMaintenance: 1619559160
places.history.expiration.transient_current_max_pages: 143081
plugin.disable_full_page_plugin_for_types: audio/mpeg,audio/x-mpeg,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
plugin.importedState: true
plugin.state.java: 0
plugin.state.np-mswmp: 2
plugin.state.npctrl: 2
plugins.click_to_play: false
print.print_printer: HP Color LaserJet 2840 series PCL 6
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_bgcolor: false
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_bgimages: false
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_command:
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_downloadfonts: false
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_edge_bottom: 0
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_edge_left: 0
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_edge_right: 0
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_edge_top: 0
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_evenpages: true
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_footercenter:
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_footerleft: &PT
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_footerright: &D
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_headercenter:
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_headerleft: &T
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_headerright: &U
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_in_color: true
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_margin_bottom: 0.5
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_margin_left: 0.5
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_margin_right: 0.5
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_margin_top: 0.5
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_oddpages: true
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_orientation: 0
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_pagedelay: 500
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_paper_data: 9
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_paper_height: 11,00
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_paper_size_type: 0
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_paper_size_unit: 1
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_paper_width: 8,50
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_reversed: false
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_scaling: 1,00
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_shrink_to_fit: true
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_to_file: false
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_unwriteable_margin_bottom: 0
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_unwriteable_margin_left: 0
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_unwriteable_margin_right: 0
print.printer_HP_Color_LaserJet_2840_series_PCL_6.print_unwriteable_margin_top: 0
print.printer_HP_Officejet_J6400_series.print_bgcolor: false
print.printer_HP_Officejet_J6400_series.print_bgimages: false
print.printer_HP_Officejet_J6400_series.print_colorspace:
print.printer_HP_Officejet_J6400_series.print_command:
print.printer_HP_Officejet_J6400_series.print_downloadfonts: false
print.printer_HP_Officejet_J6400_series.print_duplex: 0
print.printer_HP_Officejet_J6400_series.print_edge_bottom: 0
print.printer_HP_Officejet_J6400_series.print_edge_left: 0
print.printer_HP_Officejet_J6400_series.print_edge_right: 0
print.printer_HP_Officejet_J6400_series.print_edge_top: 0
print.printer_HP_Officejet_J6400_series.print_evenpages: true
print.printer_HP_Officejet_J6400_series.print_footercenter:
print.printer_HP_Officejet_J6400_series.print_footerleft: &PT
print.printer_HP_Officejet_J6400_series.print_footerright: &D
print.printer_HP_Officejet_J6400_series.print_headercenter:
print.printer_HP_Officejet_J6400_series.print_headerleft: &T
print.printer_HP_Officejet_J6400_series.print_headerright: &U
print.printer_HP_Officejet_J6400_series.print_in_color: true
print.printer_HP_Officejet_J6400_series.print_margin_bottom: 0.5
print.printer_HP_Officejet_J6400_series.print_margin_left: 0.5
print.printer_HP_Officejet_J6400_series.print_margin_right: 0.5
print.printer_HP_Officejet_J6400_series.print_margin_top: 0.5
print.printer_HP_Officejet_J6400_series.print_oddpages: true
print.printer_HP_Officejet_J6400_series.print_orientation: 0
print.printer_HP_Officejet_J6400_series.print_page_delay: 50
print.printer_HP_Officejet_J6400_series.print_pagedelay: 500
print.printer_HP_Officejet_J6400_series.print_paper_data: 9
print.printer_HP_Officejet_J6400_series.print_paper_height: 11,00
print.printer_HP_Officejet_J6400_series.print_paper_name:
print.printer_HP_Officejet_J6400_series.print_paper_size_type: 0
print.printer_HP_Officejet_J6400_series.print_paper_size_unit: 1
print.printer_HP_Officejet_J6400_series.print_paper_width: 8,50
print.printer_HP_Officejet_J6400_series.print_plex_name:
print.printer_HP_Officejet_J6400_series.print_resolution: 0
print.printer_HP_Officejet_J6400_series.print_resolution_name:
print.printer_HP_Officejet_J6400_series.print_reversed: false
print.printer_HP_Officejet_J6400_series.print_scaling: 1,00
print.printer_HP_Officejet_J6400_series.print_shrink_to_fit: true
print.printer_HP_Officejet_J6400_series.print_to_file: false
print.printer_HP_Officejet_J6400_series.print_unwriteable_margin_bottom: 0
print.printer_HP_Officejet_J6400_series.print_unwriteable_margin_left: 0
print.printer_HP_Officejet_J6400_series.print_unwriteable_margin_right: 0
print.printer_HP_Officejet_J6400_series.print_unwriteable_margin_top: 0
privacy.clearOnShutdown.downloads: false
privacy.clearOnShutdown.formdata: false
privacy.clearOnShutdown.history: false
privacy.clearOnShutdown.sessions: false
privacy.cpd.downloads: false
privacy.cpd.formdata: false
privacy.cpd.history: false
privacy.cpd.sessions: false
privacy.donottrackheader.enabled: true
privacy.item.cookies: true
privacy.item.formdata: false
privacy.item.history: false
privacy.item.sessions: false
privacy.sanitize.migrateClearSavedPwdsOnExit: true
privacy.sanitize.migrateFx3Prefs: true
privacy.sanitize.promptOnSanitize: false
privacy.sanitize.sanitizeOnShutdown: true
privacy.trackingprotection.enabled: true
privacy.trackingprotection.introCount: 20
security.disable_button.openCertManager: false
security.sandbox.content.tempDirSuffix: {d719d5e2-73fd-4924-be9b-300e85bd5139}
security.ssl.errorReporting.automatic: true
security.warn_entering_secure: true
security.warn_leaving_secure: true
security.warn_viewing_mixed: false
services.sync.declinedEngines:
storage.vacuum.last.index: 1
storage.vacuum.last.places.sqlite: 1619559160

Preferenze importanti bloccate
------------------------------

Database Places
---------------

JavaScript
----------

GC incrementale: true

Accessibilità
-------------

Attivato: false
Impedisci accessibilità: 0

Versioni librerie
-----------------

NSPR
Versione minima prevista: 4.13.1
Versione in uso: 4.13.1

NSS
Versione minima prevista: 3.28.3
Versione in uso: 3.28.3

NSSSMIME
Versione minima prevista: 3.28.3
Versione in uso: 3.28.3

NSSSSL
Versione minima prevista: 3.28.3
Versione in uso: 3.28.3

NSSUTIL
Versione minima prevista: 3.28.3
Versione in uso: 3.28.3

Caratteristiche sperimentali
----------------------------

Sandbox
-------

Livello sandbox content process: 1

Updated

2 years ago
Flags: needinfo?(condacum)

Comment 74

2 years ago
(In reply to Kan-Ru Chen [:kanru] (UTC+8) from comment #72)
> Could you describe your environment with more details? For example how many
> tabs were opened when you were closing Firefox? Can you reproduce it with
> addons disabled? It will help us understand the issue and increase the
> possibility of getting this fixed. It will help if you have clear steps to
> reproduce the issue.
> 
> You can also attach the content from about:support page here or mail it to
> me directly.

kanru: You didn't ask input of me, but I'll add it anyway -- as I've seen this crash daily for more than a year, 3 - 4 times per day. They happen when Firefox updates itself (like clockwork!) and often when I close Nightly. I have maybe 4 - 20 tabs active at any one time, have made fresh profiles, etc. None of that affects whether I crash. Additionally, these crashes are (for me) unannounced; I know of them only because of about:crashes.

STR? Simple: let Nightly update itself. It seems that simply shutting down Nightly also provokes a crash.


Application Basics
------------------

Name: Firefox
Version: 55.0a1
Build ID: 20170312030213
Update Channel: nightly
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0) Gecko/20100101 Firefox/55.0
OS: Darwin 16.4.0
Multiprocess Windows: 1/1 (Enabled by default)
Google Key: Found
Mozilla Location Service Key: Found
Safe Mode: false

Crash Reports for the Last 3 Days
---------------------------------

Report ID: bp-ab705c52-0c6e-4322-861c-fe6eb2170312
Submitted: 17 hours ago

Report ID: bp-46001874-600f-4af6-8e09-125d52170312
Submitted: 17 hours ago

Report ID: bp-a477cbbd-f319-4803-a9f3-a3ae72170312
Submitted: 17 hours ago

Report ID: bp-ff05ff0e-6905-4c62-a26e-fb1382170312
Submitted: 17 hours ago

Report ID: bp-7a4d0265-c026-4c4c-b59a-dabbb2170311
Submitted: 2 days ago

Report ID: bp-396b9dce-dc18-4a0c-b9dc-ab1a92170311
Submitted: 2 days ago

Report ID: bp-a1e9c26c-cb50-4d9c-b20b-b2ca72170311
Submitted: 2 days ago

Report ID: bp-f75a2339-2a8c-4005-929b-459f52170311
Submitted: 2 days ago

Report ID: bp-0c37bf8e-1c78-4502-9107-aba7d2170310
Submitted: 3 days ago

Report ID: bp-820c610c-1fc5-4584-be24-3ddfa2170310
Submitted: 3 days ago

Report ID: bp-1fe8820b-5490-4cd5-b657-fcddd2170310
Submitted: 3 days ago

Report ID: bp-cfcfc73e-ba96-4832-93c1-97dc22170310
Submitted: 3 days ago

Report ID: bp-9e279adc-5a2f-4994-900a-f3de52170310
Submitted: 3 days ago

Report ID: bp-30d3d5b7-0c05-4cd7-b782-850c62170310
Submitted: 3 days ago

Report ID: bp-653ad142-ade9-4602-99ff-98bc12170310
Submitted: 3 days ago

Report ID: bp-746f997e-f51f-4f57-af23-fa0af2170310
Submitted: 3 days ago

All Crash Reports

Extensions
----------

Name: About Sync extension for Firefox
Version: 0.0.8
Enabled: true
ID: aboutsync@mhammond.github.com

Name: Activity Stream
Version: 0.0.0
Enabled: true
ID: activity-stream@mozilla.org

Name: Activity Stream
Version: 1.6.0
Enabled: true
ID: @activity-streams

Name: Adobe Acrobat DC - Create PDF
Version: 15.01.02
Enabled: true
ID: web2pdfextension@web2pdf.adobedotcom

Name: All Tabs Helper
Version: 0.2.34
Enabled: true
ID: alltabshelper@alltabshelper.org

Name: Application Update Service Helper
Version: 2.0
Enabled: true
ID: aushelper@mozilla.org

Name: FireQuery
Version: 2.0.4
Enabled: true
ID: firequery@binaryage.com

Name: FlyWeb
Version: 1.0.0
Enabled: true
ID: flyweb@mozilla.org

Name: Form Autofill
Version: 1.0
Enabled: true
ID: formautofill@mozilla.org

Name: Multi-process staged rollout
Version: 1.11
Enabled: true
ID: e10srollout@mozilla.org

Name: Nightly Tester Tools
Version: 3.9
Enabled: true
ID: {8620c15f-30dc-4dba-a131-7c5d20cf4a29}

Name: Open Tabs Next to Current
Version: 1.1.5
Enabled: true
ID: opentabsnexttocurrent@sblask

Name: Places Maintenance
Version: 2.0.2
Enabled: true
ID: places-maintenance@bonardo.net

Name: Pocket
Version: 1.0.5
Enabled: true
ID: firefox@getpocket.com

Name: Presentation
Version: 1.0.0
Enabled: true
ID: presentation@mozilla.org

Name: Send Tab to Device
Version: 0.7.1-signed.1-signed
Enabled: true
ID: jid1-mdjmA7if6lo8lA@jetpack

Name: Session Manager
Version: 0.8.1.13
Enabled: true
ID: {1280606b-2510-4fe0-97ef-9b5a22eafe30}

Name: Shield Recipe Client
Version: 1.0.0
Enabled: true
ID: shield-recipe-client@mozilla.org

Name: snoozetabs
Version: 1.0.14
Enabled: true
ID: snoozetabs@mozilla.com

Name: Tab Groups
Version: 2.1.4
Enabled: true
ID: tabgroups@quicksaver

Name: Test Pilot
Version: 1.1.1-dev-97fd716
Enabled: true
ID: @testpilot-addon

Name: Web Compat
Version: 1.1
Enabled: true
ID: webcompat@mozilla.org

Name: WebCompat Reporter
Version: 1.0.0
Enabled: true
ID: webcompat-reporter@mozilla.org

Name: LiveReload
Version: 2.1.1
Enabled: false
ID: livereload@livereload.com

Graphics
--------

Features
Compositing: OpenGL
Asynchronous Pan/Zoom: wheel input enabled; scrollbar drag enabled
WebGL 1 Driver WSI Info: CGL
WebGL 1 Driver Renderer: ATI Technologies Inc. -- AMD Radeon Pro 460 OpenGL Engine
WebGL 1 Driver Version: 2.1 ATI-1.48.21
WebGL 1 Driver Extensions: GL_ARB_color_buffer_float GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_seamless_cube_map GL_ARB_shader_objects GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_non_power_of_two GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_transpose_matrix GL_ARB_vertex_array_bgra GL_ARB_vertex_blend GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_depth_bounds_test GL_EXT_draw_buffers2 GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture_array GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc GL_EXT_texture_env_add GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_rectangle GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_timer_query GL_EXT_transform_feedback GL_EXT_vertex_array_bgra GL_APPLE_aux_depth_stencil GL_APPLE_client_storage GL_APPLE_element_array GL_APPLE_fence GL_APPLE_float_pixels GL_APPLE_flush_buffer_range GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_packed_pixels GL_APPLE_pixel_buffer GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_specular_vector GL_APPLE_texture_range GL_APPLE_transform_hint GL_APPLE_vertex_array_object GL_APPLE_vertex_array_range GL_APPLE_vertex_point_size GL_APPLE_vertex_program_evaluators GL_APPLE_ycbcr_422 GL_ATI_blend_equation_separate GL_ATI_blend_weighted_minmax GL_ATI_separate_stencil GL_ATI_texture_compression_3dc GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_ATI_texture_mirror_once GL_IBM_rasterpos_clip GL_NV_blend_square GL_NV_conditional_render GL_NV_depth_clamp GL_NV_fog_distance GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_barrier GL_SGI_color_matrix GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod
WebGL 1 Extensions: ANGLE_instanced_arrays EXT_blend_minmax EXT_color_buffer_half_float EXT_frag_depth EXT_sRGB EXT_shader_texture_lod EXT_texture_filter_anisotropic MOZ_debug_get OES_element_index_uint OES_standard_derivatives OES_texture_float OES_texture_float_linear OES_texture_half_float OES_texture_half_float_linear OES_vertex_array_object WEBGL_color_buffer_float WEBGL_compressed_texture_s3tc WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_depth_texture WEBGL_draw_buffers WEBGL_lose_context MOZ_WEBGL_lose_context MOZ_WEBGL_compressed_texture_s3tc MOZ_WEBGL_depth_texture
WebGL 2 Driver WSI Info: CGL
WebGL 2 Driver Renderer: ATI Technologies Inc. -- AMD Radeon Pro 460 OpenGL Engine
WebGL 2 Driver Version: 4.1 ATI-1.48.21
WebGL 2 Driver Extensions: GL_ARB_blend_func_extended GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_ES2_compatibility GL_ARB_explicit_attrib_location GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader5 GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_occlusion_query2 GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_subroutine GL_ARB_shading_language_include GL_ARB_tessellation_shader GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_cube_map_array GL_ARB_texture_gather GL_ARB_texture_query_lod GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_swizzle GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_vertex_attrib_64bit GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_depth_bounds_test GL_EXT_texture_compression_s3tc GL_EXT_texture_filter_anisotropic GL_EXT_texture_mirror_clamp GL_EXT_texture_sRGB_decode GL_APPLE_client_storage GL_APPLE_container_object_shareable GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_texture_range GL_ATI_texture_mirror_once GL_NV_texture_barrier
WebGL 2 Extensions: EXT_color_buffer_float EXT_texture_filter_anisotropic EXT_disjoint_timer_query MOZ_debug_get OES_texture_float_linear WEBGL_compressed_texture_s3tc WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_lose_context MOZ_WEBGL_lose_context MOZ_WEBGL_compressed_texture_s3tc
Audio Backend: audiounit
GPU #1
Active: Yes
Vendor ID: 0x1002
Device ID: 0x67ef

Diagnostics
AzureCanvasAccelerated: 1
AzureCanvasBackend: skia
AzureContentBackend: skia
AzureFallbackCanvasBackend: none
TileHeight: 1024
TileWidth: 1024
Decision Log
WEBRENDER:
unavailable by runtime: Build doesn't include WebRender




Important Modified Preferences
------------------------------

accessibility.typeaheadfind.flashBar: 0
browser.cache.disk.capacity: 358400
browser.cache.disk.filesystem_reported: 1
browser.cache.disk.hashstats_reported: 1
browser.cache.disk.smart_size.first_run: false
browser.cache.disk.smart_size.use_old_max: false
browser.cache.frecency_experiment: 2
browser.download.importedFromSqlite: true
browser.places.smartBookmarksVersion: 8
browser.sessionstore.upgradeBackup.latestBuildID: 20170312030213
browser.startup.homepage: resource://activity-streams/data/content/activity-streams.html#/
browser.startup.homepage_override.buildID: 20170312030213
browser.startup.homepage_override.mstone: 55.0a1
browser.tabs.crashReporting.includeURL: true
browser.tabs.drawInTitlebar: false
browser.urlbar.maxRichResults: 12
browser.urlbar.suggest.searches: true
browser.urlbar.usepreloadedtopurls.enabled: false
dom.gamepad.extensions.enabled: true
dom.ipc.processCount: 4
dom.push.userAgentID: f5444e6008f44158ad9e57f428476069
extensions.lastAppVersion: 55.0a1
font.internaluseonly.changed: true
media.benchmark.vp9.fps: 204
media.benchmark.vp9.versioncheck: 2
media.gmp-gmpopenh264.abi: x86_64-gcc3
media.gmp-gmpopenh264.lastUpdate: 1481375856
media.gmp-gmpopenh264.version: 1.6
media.gmp-manager.buildID: 20170312030213
media.gmp-manager.lastCheck: 1489342030
media.gmp-widevinecdm.abi: x86_64-gcc3
media.gmp-widevinecdm.lastUpdate: 1481375858
media.gmp-widevinecdm.version: 1.4.8.903
media.gmp.storage.version.observed: 1
network.cookie.prefsMigrated: true
network.predictor.cleaned-up: true
places.database.lastMaintenance: 1489171220
places.favicons.optimizeToDimension: 64
places.history.expiration.transient_current_max_pages: 87071
plugin.disable_full_page_plugin_for_types: application/pdf
print.printer__.print_bgcolor: false
print.printer__.print_bgimages: false
print.printer__.print_duplex: -437918235
print.printer__.print_edge_bottom: 0
print.printer__.print_edge_left: 0
print.printer__.print_edge_right: 0
print.printer__.print_edge_top: 0
print.printer__.print_evenpages: true
print.printer__.print_footercenter:
print.printer__.print_footerleft: &PT
print.printer__.print_footerright: &D
print.printer__.print_headercenter:
print.printer__.print_headerleft: &T
print.printer__.print_headerright: &U
print.printer__.print_in_color: true
print.printer__.print_margin_bottom: 0.5
print.printer__.print_margin_left: 0.5
print.printer__.print_margin_right: 0.5
print.printer__.print_margin_top: 0.5
print.printer__.print_oddpages: true
print.printer__.print_orientation: 0
print.printer__.print_page_delay: 50
print.printer__.print_paper_data: 0
print.printer__.print_paper_height: 11.00
print.printer__.print_paper_name: na-letter
print.printer__.print_paper_size_unit: 0
print.printer__.print_paper_width: 8.50
print.printer__.print_resolution: -437918235
print.printer__.print_reversed: false
print.printer__.print_scaling: 1.00
print.printer__.print_shrink_to_fit: true
print.printer__.print_to_file: false
print.printer__.print_unwriteable_margin_bottom: 56
print.printer__.print_unwriteable_margin_left: 25
print.printer__.print_unwriteable_margin_right: 25
print.printer__.print_unwriteable_margin_top: 25
privacy.cpd.extensions-sessionmanager: false
privacy.cpd.formdata: false
privacy.cpd.offlineApps: true
privacy.popups.showBrowserMessage: false
privacy.sanitize.timeSpan: 0
security.sandbox.content.tempDirSuffix: {7d405653-de88-074c-9cc2-b4e6c9f9fd59}
services.sync.declinedEngines:
services.sync.engine.prefs.modified: false
services.sync.lastPing: 1489341901
services.sync.lastSync: Mon Mar 13 2017 07:28:37 GMT-0400 (EDT)
services.sync.numClients: 4
social.enabledByActivityStream: true
storage.vacuum.last.index: 1
storage.vacuum.last.places.sqlite: 1488402289

Important Locked Preferences
----------------------------

Places Database
---------------

JavaScript
----------

Incremental GC: true

Accessibility
-------------

Activated: false
Prevent Accessibility: 0

Library Versions
----------------

NSPR
Expected minimum version: 4.13.1
Version in use: 4.13.1

NSS
Expected minimum version: 3.30 Beta
Version in use: 3.30 Beta

NSSSMIME
Expected minimum version: 3.30 Beta
Version in use: 3.30 Beta

NSSSSL
Expected minimum version: 3.30 Beta
Version in use: 3.30 Beta

NSSUTIL
Expected minimum version: 3.30 Beta
Version in use: 3.30 Beta

Experimental Features
---------------------

Sandbox
-------

Content Process Sandbox Level: 2

Comment 75

2 years ago
Frank, can you confirm that just now 
	Virtual_ManPL [:Virtual] - (ni? me) 
fixed this bug?
because just now I received some very strange notification per email.
https://bugzilla.mozilla.org/show_bug.cgi?id=1331929
https://bugzilla.mozilla.org/show_bug.cgi?id=1311297

Updated

2 years ago
Flags: needinfo?(burleigh)

Comment 76

2 years ago
(In reply to Yorgos from comment #75)
> Frank, can you confirm that just now 
> 	Virtual_ManPL [:Virtual] - (ni? me) 
> fixed this bug?
> because just now I received some very strange notification per email.
> https://bugzilla.mozilla.org/show_bug.cgi?id=1331929
> https://bugzilla.mozilla.org/show_bug.cgi?id=1311297

Yorgos: I would stay tuned to this bug, and ignore changes to the two bugs you list. It's likely a Mozilla process is simply closing related, inactive, unhelpful or duplicate bugs with no action. Problems like this that many people have generate a lot of noise, so now and then that noise has to be cleared away so it doesn't distract from real work. IMHO, of course.
Flags: needinfo?(burleigh)
Exactly it's like Frank Burleigh said.
There is no need to create many duplicate bugs about the same issue, as they pollute related bugs in crashlog reports, making hard to speedy find anything in all that useless spam.

About bugs I marked as INCOMPLETE, they have noSTR from OP.

Reproducible bugs are tracked in blocked bug #1219672.


tl;dr - I'm cleaning.



(In reply to Yorgos from comment #75)
> fixed
more like, I marked them as INCOMPLETE

Comment 79

2 years ago
I pasted the link here because the log (crash report) told me "NEW", not Duplicate ;) otherwise I know that I dont need to post in a duplicate thread!

Comment 80

2 years ago
Virtual: I'm MacOS (OS X), so platform should perhaps be adjusted.
Don't worry, I want all these bugs to be fixed like you too, that's why I'm doing "a little cleaning" (I hope I didn't make any mistakes in this), to help Mozilla developers (or at least I think that I'm helping) getting on track faster without reading duplicates, etc.
status-firefox49: affected → wontfix
status-firefox52: --- → affected
status-firefox53: --- → affected
status-firefox54: --- → affected
status-firefox55: --- → affected
status-firefox-esr52: --- → affected
Keywords: crash, crashreportid, multiprocess
OS: Windows 7 → All
Hardware: x86 → All

Comment 82

2 years ago
For me it crashes in FF Nightly as well.
https://crash-stats.mozilla.com/report/index/3f346172-bf3b-4869-b2d9-7f4ce2170329
Mass wontfix for bugs affecting firefox 52.
status-firefox52: affected → wontfix
Any news to this bug?

278934 crashes of this sig in the last 7 days.
https://crash-stats.mozilla.com/signature/?product=Firefox&signature=IPCError-browser%20%7C%20ShutDownKill
status-firefox51: affected → wontfix
status-firefox-esr45: affected → wontfix
status-firefox-esr52: affected → wontfix
Keywords: topcrash
Version: 48 Branch → 38 Branch

Comment 86

2 years ago
Signature report for IPCError-browser | ShutDownKill

Showing results from 7 days ago 

Operating System
Windows 7 	46211 	46.5%
Windows 10 	29388 	29.6%
Windows 8.1 	11219 	11.3%
        	3429 	3.5%
OS X 10.12 	2899 	2.9%
Windows 8 	2313 	2.3%
OS X 10.11 	1097 	1.1%
Linux   	1011 	1.0%

Product
Firefox 	54.0a2 	37251 	37.5% 	9618
Firefox 	55.0a1 	24892 	25.1% 	10359
Firefox 	54.0b4 	12112 	12.2% 	4892
Firefox 	54.0b3 	4570 	4.6% 	3417
Firefox 	54.0b2 	2587 	2.6% 	1752
Firefox 53.0b99 	2576 	2.6% 	807
Firefox 	54.0b1 	2139 	2.2% 	1664
Firefox 	54.0a1 	1082 	1.1% 	90
Firefox 	53.0b9 	1003 	1.0% 	769

Process Type
content 	99347 	100.0%

Uptime Range
> 1 hour 	46403 	46.7%
< 1 min 	26264 	26.4%
15-60 min 	12102 	12.2%
1-5 min 	8937 	9.0%
5-15 min 	5645 	5.7%

Architecture
x86 	61358 	61.8%
amd64 	34564 	34.8%
	3429 	3.5%

Flash Version
[blank] 	95922 	96.5%
        	3429 	3.5%
Yeah, it's going down! :-) 80386 crashes in the last 7 days.

When it is also caused by add-ons that are not multiprocessor compatible, whats about deactivate such add-ons in the Developer Edition, too? Developers should be able to set extensions.allow-non-mpc-extensions=true in about:config, too.

Also: Is it possible to activate this signature in https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=55.0a1&days=7 again, to have a better eye on it?
Keywords: qawanted
I still see a clear relation between a high memory usage of FF after a long time use of GMail, Twitter or Facebook and the ShutDownKills that appear by the restart/shutdown after them. I guess fixing those ShutDownKill-Crashes will reduce the amount of memory FF use over the time it runs and reduce the need to restart FF between work.

Here are some sample crash reports from me for analyses produced with FF55.0a1, 64bit, E10s, on Win7 from the last days with different threads:
https://crash-stats.mozilla.com/report/index/b232d572-a9a3-45b6-9662-7b9fa0170602
https://crash-stats.mozilla.com/report/index/d9c58c40-fea7-4791-bc8a-b9d930170602
https://crash-stats.mozilla.com/report/index/c1293857-e13c-405b-b682-0bd590170602
https://crash-stats.mozilla.com/report/index/fbc04e1b-03e6-419d-98d6-8e8610170601
https://crash-stats.mozilla.com/report/index/d0a2f888-28f9-4ce7-a4eb-9a9980170601
https://crash-stats.mozilla.com/report/index/12dc4eb5-1fd0-4508-aaf1-4887b0170601
https://crash-stats.mozilla.com/report/index/f683fb5e-4269-405a-949a-ded770170531
https://crash-stats.mozilla.com/report/index/33f8b46d-1035-422b-a2d2-4c6940170531
https://crash-stats.mozilla.com/report/index/3c87e99e-ed67-4140-9b98-3e9a60170531

(In reply to Tobias B. Besemer [:BesTo] (QA) from comment #88)
> When it is also caused by add-ons that are not multiprocessor compatible,
> whats about deactivate such add-ons in the Developer Edition, too?
> Developers should be able to set extensions.allow-non-mpc-extensions=true in
> about:config, too.
When aurora is not used to ship a alpha2 to developers ATM (is FF54.0a2 while beta is FF54.0bx), what's about shipping FF55.0a1 also as FF55.0a2 to devs ATM? This would force devs to have an eye on webextension/multi-processor-compatibility of there extension. Should I fill a new bug for it?

> Also: Is it possible to activate this signature in
> https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=55.
> 0a1&days=7 again, to have a better eye on it?
Should I fill a new bug for it, too?
Flags: needinfo?(wmccloskey)
Here are from me some sample-reports with different threads of new crash-variants from the last days produced with FF55.0a1 latest versions, 64bit with E10s, on Win7, for analyses:
https://crash-stats.mozilla.com/report/index/22efc755-adc8-4cd2-ad57-3a9710170612
https://crash-stats.mozilla.com/report/index/2656bddf-bbd3-4ed8-a81b-45ec20170612
https://crash-stats.mozilla.com/report/index/3102b8b2-a3c0-4e91-aee4-518960170611
https://crash-stats.mozilla.com/report/index/300cff78-bc3e-48e7-8ce6-923840170611

Stats are now: 52101 crashes in the last 7 days
Posting links to crash reports is not useful, without any additional information. If somebody is interested in looking at this issue, they can use crash-stats to find reports.
status-firefox56: --- → affected
status-firefox53: affected → wontfix
QA Contact: Tobias.Besemer
More then 243k crashes with this sig in the last 7 days!
Somebody still analyzing them?
(In reply to Tobias B. Besemer [:BesTo] (QA) from comment #94)
> More then 243k crashes with this sig in the last 7 days!
> Somebody still analyzing them?

Hey Tobias, this is a very generic signature that corresponds to crashes (less severe than others, as they occur during shutdown) with very different causes.
We are monitoring it to see if new crash causes occur (e.g. we recently filed bug 1375704).

If you find a reproducible case, please file a new bug and describe the STR. Otherwise, there's no need to keep updating this bug.

(In reply to Tobias B. Besemer [:BesTo] (QA) from comment #88)
> Also: Is it possible to activate this signature in
> https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=55.
> 0a1&days=7 again, to have a better eye on it?

This is a content process crash, that page shows parent process crashes. If you want a view with this signature in it, you can use https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=55.0a1&days=7&process_type=content.
Flags: needinfo?(wmccloskey)
(In reply to Marco Castelluccio [:marco] from comment #95)
> Hey Tobias, [...]
> We are monitoring it to see if new crash causes occur (e.g. we recently
> filed bug 1375704).
> If you find a reproducible case, please file a new bug and describe the STR.
> Otherwise, there's no need to keep updating this bug.

Marco, thx for you help!

If I find a proto_signature (like: proto_signature=~WaitForSyncNotifyWithA11yReentry) I always get and can monitor this way too, can I fill also a bug for it if the proto_signature have many crashes?

---

Bugs for IPCError-browser | ShutDownKill:
    1339589 NEW --- Firefox on Windows with a11y features enabled crashes on certain websites
    1333605 NEW --- Crash in IPCError-browser | ShutDownKill when GCing
    1333464 NEW --- Crash in [@ IPCError-browser | ShutDownKill ] caused by the Gecko Profiler
    1329305 RESOLVED FIXED Crash in IPCError-browser | ShutDownKill (from GPUVideoImage::GetAsSourceSurface)
    1329301 NEW --- Crash in IPCError-browser | ShutDownKill (from GfxInfoBase::GetFeatureStatus)
    1329300 RESOLVED FIXED Crash in IPCError-browser | ShutDownKill | I422ToARGBRow_C
    1324820 RESOLVED FIXED IPCError-browser | ShutDownKill received when closing FX while a gif is autoplaying from Twitter moments
    1324399 NEW --- Shutdown hang crash after DownThemAll! *nightly* extension update
    1316867 NEW --- Deterministic crash from cycle collector to js::Scope::traceChildren() when running wasm content
    1311869 NEW --- FireFox 49.0.2 Denial Of Service
    1290280 VERIFIED FIXED [e10s] Tab crashes on startup
    1289405 NEW --- Restarts to update and quits frequently spin for extended/indefinite time after all windows closed
    1279293 NEW --- Crash in IPCError-browser | ShutDownKill
    1266275 RESOLVED DUPLICATE crash in WaitForSingleObjectEx | WaitForSingleObject | PR_WaitCondVar | mozilla::CondVar::Wait | mozilla::ipc::MessageChannel::WaitForSyncNotify | mozilla::ipc::MessageChannel::Send | mozilla::net::PCookieServiceChild::SendGetCookieString
    1259125 NEW --- crash in nsINode::Slots
    1240542 NEW --- crash in js::InterpreterActivation::InterpreterActivation
    1238657 NEW --- crash in js::frontend::TokenStream::getChar
    1219672 NEW --- [meta] e10s related ShutDownKill parent side abort of the content process
    1200646 NEW --- crash in DestroyDisplayItemDataForFrames
Summary: Crash in IPCError-browser | ShutDownKill → [meta] Crash in [@ IPCError-browser | ShutDownKill]
(In reply to Tobias B. Besemer [:BesTo] (QA) from comment #96)
> (In reply to Marco Castelluccio [:marco] from comment #95)
> > Hey Tobias, [...]
> > We are monitoring it to see if new crash causes occur (e.g. we recently
> > filed bug 1375704).
> > If you find a reproducible case, please file a new bug and describe the STR.
> > Otherwise, there's no need to keep updating this bug.
> 
> Marco, thx for you help!
> 
> If I find a proto_signature (like:
> proto_signature=~WaitForSyncNotifyWithA11yReentry) I always get and can
> monitor this way too, can I fill also a bug for it if the proto_signature
> have many crashes?

No, unless you have steps to reproduce or the crash is exploding (that is, if it was low-volume and suddenly became high volume).

Updated

a year ago
Depends on: 1378276
I have a low-powered AMD Brazos E-350-based laptop (Lenovo x120e) and I get the crash infobar on every restart.

Having a fixed value for dom.ipc.tabs.shutdownTimeoutSecs is unreasonable. It should be based on CPU performance.

Comment 100

a year ago
Signature report for IPCError-browser | ShutDownKill
Showing results from 7 days ago

760,549 Results 

Windows 7 	432449 	57.2%
______	172851 	22.8%
Windows 10 	69528 	9.2%
Windows 8.1 	60316 	8.0%
Windows 8 	11046 	1.5%
Linux	 	5114 	0.7%
OS X 10.12 	2499 	0.3%
OS X 10.11 	906 	0.1%
Windows XP 	717 	0.1%
OS X 10.10 	405 	0.1%
OS X 10.13 	343 	0.0%
OS X 10.9 	168 	0.0%
Windows Vista 	141 	0.0%
OS X 10.7 	49 	0.0%
Windows Server 2003 	7 	0.0%

Product
Firefox 	58.0a1 	29766 	3.9% 	14975
Firefox 	57.0b4 	1490 	0.2% 	770
Firefox 	57.0b3 	235271 	31.1% 	58808
Firefox 	57.0b0 	26731 	3.5% 	6502
________	57.0b0 	2 	0.0% 	2
Firefox 	57.0a1 	7039 	0.9% 	3237
Firefox 	56.0b99	280748 	37.1% 	52273
Firefox 	56.0b12	72465 	9.6% 	25662
Firefox 	56.0b11	18920 	2.5% 	5869
Firefox 	56.0b10	13566 	1.8% 	5072

Uptime Range
> 1 hour 	411879 	54.4%
< 1 min 	142035 	18.8%
15-60 min 	119670 	15.8%
1-5 min 	43869 	5.8%
5-15 min 	39086 	5.2%

Architecture
x86 	433124 	57.3%
_____	172851 	22.8%
amd64 	150564 	19.9%

Flash Version
[blank] 	756524 	100.0%
27.0.0.130 	12 	0.0%
11.8.800.168 	1 	0.0%
26.0.0.151 	1 	0.0%
27.0.0.151 	1 	0.0%

Graphics Adapter
0x8086 	0x29c2 	48514 	6.4%
0x8086 	0x2e32 	43141 	5.7%
0x8086 	0x0152 	39741 	5.3%
0x8086 	0x0102 	34138 	4.5%
0x8086 	0x2a42 	28727 	3.8%
0x8086 	0x2772 	27883 	3.7%
0x8086 	0x0166 	26806 	3.5%
0x8086 	0x0f31 	26451 	3.5%
0x8086 	0x0046 	26235 	3.5%
0x8086 	0x0116 	24699 	3.3%
0x8086 	0x0a16 	23631 	3.1%
status-firefox57: --- → affected
status-firefox58: --- → affected

Updated

a year ago
Depends on: 1406839

Comment 101

a year ago
[Tracking Requested - why for this release]:

Can this [meta] bug and all of the individual bugs that "depend" on it be tracked for FF58?

There are hundreds of thousands of crashes under this signature in the past 7 days often accounting for upwards of 90% of the content crashes per release.

It is the #1 Top Crasher for Content crashes. 

Signature report for IPCError-browser | ShutDownKill
Showing results from 7 days ago
962,573 Results	

[IPCError-browser | ShutDownKill]

https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=58.0a1&days=7&process_type=content

Top Crashers for Firefox 58.0a1
1 	67.52% 	-6.31% 	IPCError-browser | ShutDownKill
	39573 	27710 	697 	2166 	15650 	0 	2016-05-04 	

https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=57.0b6&days=7&process_type=content

Top Crashers for Firefox 57.0b6
1 	10.16% 	new 	IPCError-browser | ShutDownKill
	1978 	1490 	10 	35 	585 	0 	2016-05-04 	
2 	8.12% 	new 	IPCError-browser | PBrowserParent::RecvPDocAccessibleConstructor Constructing a top-level PDocAccessible with null COM
	1582 	1582 	0 	0 	392 	0 	2017-05-02 	
	
https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=57.0b5&days=7&process_type=content

Top Crashers for Firefox 57.0b5
1 	89.81% 	-32.67% 	IPCError-browser | ShutDownKill
	408160 	307837 	827 	1042 	85982 	0 	2016-05-04
2 	2.75% 	new 	IPCError-browser | PBrowserParent::RecvPDocAccessibleConstructor Constructing a top-level PDocAccessible with null COM
	12480 	12461 	0 	0 	609 	0 	2017-05-02 

https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=57.0b4&process_type=content

Top Crashers for Firefox 57.0b4
1 	92.62% 	-4.41% 	IPCError-browser | ShutDownKill
	268636 	201086 	592 	361 	81244 	0 	2016-05-04 
2 	2.57% 	1.79% 	IPCError-browser | PBrowserParent::RecvPDocAccessibleConstructor Constructing a top-level PDocAccessible with null COM
	7449 	7432 	0 	0 	441 	0 	2017-05-02 	

https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=57.0b3&process_type=content

Top Crashers for Firefox 57.0b3	
1 	89.14% 	-3.48% 	IPCError-browser | ShutDownKill
	63962 	46353 	592 	676 	23462 	0 	2016-05-04
2 	3.96% 	2.28% 	IPCError-browser | PBrowserParent::RecvPDocAccessibleConstructor Constructing a top-level PDocAccessible with null COM
	2840 	2837 	0 	0 	270 	0 	2017-05-02 	

https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=57.0b&process_type=content

Top Crashers for Firefox 57.0b
1 	88.73% 	-2.55% 	IPCError-browser | ShutDownKill
	742556 	555680 	2087 	3167 	194722 	0 	2016-05-04 
2 	2.9% 	2.43% 	IPCError-browser | PBrowserParent::RecvPDocAccessibleConstructor Constructing a top-level PDocAccessible with null COM
	24304 	24265 	0 	0 	1727 	0 	2017-05-02 
	
https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=57.0a1&process_type=content

Top Crashers for Firefox 57.0a1
1 	73.26% 	-2.93% 	IPCError-browser | ShutDownKill
	2219 	1495 	35 	155 	761 	0 	2016-05-04 		
	
https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=56.0.1&_facets_size=300&process_type=content

Top Crashers for Firefox 56.0.1
4 	4.71% 	new 	IPCError-browser | ShutDownKill
	23 	13 	1 	1 	18 	0 	2016-05-04 	

https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=56.0&process_type=content

Top Crashers for Firefox 56.0
1 	45.03% 	16.56% 	IPCError-browser | ShutDownKill
	70988 	53479 	193 	79 	23645 	0 	2016-05-04 

https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=56.0b12&process_type=content

Top Crashers for Firefox 56.0b12
1 	96.18% 	0.89% 	IPCError-browser | ShutDownKill
	29919 	23332 	141 	64 	13040 	0 	2016-05-04 	
	
https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=56.0b11&process_type=content

Top Crashers for Firefox 56.0b11
1 	97.57% 	-0.59% 	IPCError-browser | ShutDownKill
	12363 	9802 	49 	43 	5633 	0 	2016-05-04
Alias: IPCError_ShutDownKill
tracking-firefox58: --- → ?
No, this is a meta bug for a signature that's a catch-all for countless issues with separate root causes that aren't actually user-visible, so it's not a candidate for release tracking.  We can track specific instances where there's known STR and user impact, but otherwise there's no use.
tracking-firefox58: ? → ---

Updated

a year ago
Depends on: 1375704

Updated

a year ago
Depends on: 1408631
Duplicate of this bug: 1415837

Updated

a year ago
Depends on: 1415837
Duplicate of this bug: 1421915

Updated

a year ago
Depends on: 1421915

Updated

a year ago
Keywords: meta

Updated

11 months ago
Depends on: 1422715

Updated

11 months ago
See Also: bug 1289405

Updated

11 months ago
Depends on: 1424451

Updated

11 months ago
Depends on: 1405290

Updated

10 months ago
Duplicate of this bug: 1424451

Updated

10 months ago
Depends on: 1434319

Updated

9 months ago
Priority: P1 → P2

Updated

8 months ago
Depends on: 1437575

Updated

8 months ago
Depends on: 1358898

Updated

7 months ago
Depends on: 1445312

Updated

7 months ago
status-firefox59: --- → affected
status-firefox60: --- → affected
status-firefox61: --- → affected

Updated

7 months ago
Depends on: 1328631

Updated

7 months ago
No longer depends on: 1328631

Updated

7 months ago
Depends on: 1419488
Depends on: 1495632
You need to log in before you can comment on or make changes to this bug.