I've got an irccloud pinned tab in my Firefox on Linux (x86-64, Ubuntu 14.04). Every time I restart my browser (usually to apply a nightly update) that tab crashes immediately upon restart, without a crash report. My other tabs come up fine. Clicking "reload this tab" makes it come back up OK. I have dom.ipc.processCount set to 16.

I've never seen this one on windows or osx so it might be windows specific. Is there a chance that you can reproduce it with a debug build and get a stack from the child process? About the crash report, when you restart the browser do you get the unsent pending crash report popup at the bottom?

No, it doesn't seem to generate a crash report at all. There's nothing in about:crashes.

Oh, interestingly I have crash reports in ~/.mozilla/firefox/Crash Reports/pending/, but they don't show up in about:crashes for some reason!

It looks like the chrome process is calling mozilla::dom::ContentParent::KillHard on this content process for some reason. I don't know if there's just some weirdness with the timer on startup here? I can't seem to reproduce this with a fresh profile.

(In reply to Ted Mielczarek [:ted.mielczarek] from comment #5) > It looks like the chrome process is calling > mozilla::dom::ContentParent::KillHard on this content process for some > reason. I don't know if there's just some weirdness with the timer on > startup here? Pretty sure irccloud uses IDB. We use KillHard() in IDB in a few places: https://dxr.mozilla.org/mozilla-central/source/dom/indexedDB/ActorsParent.cpp#20194 https://dxr.mozilla.org/mozilla-central/source/dom/indexedDB/ActorsParent.cpp#20243 https://dxr.mozilla.org/mozilla-central/source/dom/indexedDB/ActorsParent.cpp#20250

(In reply to Ben Kelly [:bkelly] from comment #6) > (In reply to Ted Mielczarek [:ted.mielczarek] from comment #5) > > It looks like the chrome process is calling > > mozilla::dom::ContentParent::KillHard on this content process for some > > reason. I don't know if there's just some weirdness with the timer on > > startup here? > > Pretty sure irccloud uses IDB. We use KillHard() in IDB in a few places: > > https://dxr.mozilla.org/mozilla-central/source/dom/indexedDB/ActorsParent. > cpp#20194 > https://dxr.mozilla.org/mozilla-central/source/dom/indexedDB/ActorsParent. > cpp#20243 > https://dxr.mozilla.org/mozilla-central/source/dom/indexedDB/ActorsParent. > cpp#20250 Yeah but based on the stack it seems like the KillHard is called from a timer, no? If that is true it could be from a StartForceKillTimer... which could be a result of the frame loader being destroyed for some reason... it's hard to tell without being able to reproduce... (In reply to Ted Mielczarek [:ted.mielczarek] from comment #5) > I can't seem to reproduce this with a fresh profile. What about with a fresh profile with dom.ipc.processCount > 1 ? Or with the old profile but with all the add-ons disabled?

I tried a fresh profile with dom.ipc.processCount > 1, I'll try restarting with my existing profile with addons disabled next.

How did your experiment go? I'd love to know if you're able to reproduce with processCount = 1 as well.

This doesn't reproduce anymore. :-/