User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:42.0) Gecko/20100101 Firefox/42.0 Build ID: 20150713030204 Steps to reproduce: Visit http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=48+hours+ago&enddate=now Ctrl + Click on a bug to open it in a new tab Actual results: New Tab crashes. When I then click on any other open tab it also crashes. Clicking on restore crashed tab or restore all crashed tabs fails and tabs remain crashed Expected results: New tab should open successfully Restore tab and Restore All Tabs should work.
Using Win 10166 X64 and Nightly 42.01a X64
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
Please type about:crashes into the location bar and press Enter, then paste the relevant crash report IDs here. https://developer.mozilla.org/docs/How_to_get_a_stacktrace_for_a_bug_report Have you verified that the crashes don't occur with 32-bit Nightly? https://nightly.mozilla.org Have you verified that the crashes don't occur when “Enable multi-process Nightly” is disabled under about:preferences#general?
Severity: normal → critical
Keywords: crash, stackwanted
I hope these are correct and helpful. I have run a CCleaner + extras recently which removed a lot of the crash reports. https://crash-stats.mozilla.com/report/index/183a4da4-2529-4801-a83c-a59392150714 https://crash-stats.mozilla.com/report/index/bp-e0e00cd6-4660-48f2-ba23-1479e2150712 I'll re-enable e10's and update shortly. I'm just writing up a Google Doc report at the moment.
I have verified that the crashes don't occur when I use 32 bit version. They did occur up to Nightly ~V39 32bit but then stopped.
Karl, your crash reports here don't seem related. Since you where running tools that clear stuff off your machine, could you do me a favor? 1) go to about:crashes and click clear all reports 2) restart, confirm all crashes have been cleared 3) reproduce the crash or wait until it reproduces 4) once it reproduces grab the new about crashes link and post it here. Sound doable?
I believe its actually Lastpass that is causing the issue on certain sites. I have it set to autologin to bugzilla on my X64 Win 10. When it tries to login on certain sites it crashes the all tabs and they are not restorable without a restart of the browser Image of crash: http://imageshack.com/a/img661/928/Xd4562.png Site visited: freelancer.com Same as when I visit bugzilla and Ctrl + Click on links. Windows error reporting popped up just before the crash saying that a plugin container for nightly had crashed and it was reporting gathering info and reporting to MS. I did feel it was Lastpass that caused the issue with X86 nightly version up to verion 39, Then it stopped. I also get a "page running slowly" message on freelancer when Lastpass is logged in. This doesn't happen when it is logged off. Crash report https://crash-stats.mozilla.com/report/index/bp-183a4da4-2529-4801-a83c-a59392150714 The timestamp on this report says 3.39 a.m. but the current time is 21.36. So I don't think the crash isn't being recorded. Again this is only occurring once e10s is enabled and LastPass is logged in.
Will do now. Mid air collision :-)
I've reproduced the crash 3 times now but no crash report is being generated. On freelancer.com at least, the browser becomes extremely unresponsive with lastpass logged in and e10s enabled. Clicking through the lastpass menus to Autofill takes about 20 seconds. On clicking Autofill, all tabs crash and when I click restore all, the current tab reloads. If I then click on another tab, it starts to load but then all tabs crash again. I hope this is helpful. I'll keep trying for crash report.
I was able to capture this from Event Viewer Faulting application name: plugin-container.exe, version: 188.8.131.5273, time stamp: 0x55a5128c Faulting module name: mozglue.dll, version: 184.108.40.20673, time stamp: 0x55a4fac6 Exception code: 0x80000003 Fault offset: 0x0000000000010c07 Faulting process ID: 0x15cc Faulting application start time: 0x01d0be7666374364 Faulting application path: C:\Program Files\Nightly\plugin-container.exe Faulting module path: C:\Program Files\Nightly\mozglue.dll Report ID: 10c58c22-5734-483f-bccc-637d1b1aa63f Faulting package full name: Faulting package-relative application ID:
I have generated a new crash report https://crash-stats.mozilla.com/report/index/1db733dc-e799-4cd9-b2b5-e7a8d2150716 I hope this helps.
10 crashes on 5 different installations. (note: I think the generic signature is lack of symbols related)
Status: UNCONFIRMED → NEW
tracking-e10s: --- → +
Ever confirmed: true
I just upgraded to Windows TH 10260 and the bug seems to have stopped. I'll keep testing to make sure.
Nope...spoke too soon. Happening less frequently but still happening.
Here are a few more crash reports. It is the plugin container that stops working with LastPass. Logging off Lastpass using the icon in the browser or killing the plugin container in task manager brings FX back to life )I must restor all tabs if I kill plugin container). See crashes below; I hope they are related: bp-e8a55e72-aab0-4f24-87a5-ba0bb2150730 bp-b3494edb-92aa-450c-b4f5-3e1282150724 bp-81039be9-07d6-4fd4-ae01-5d8992150723 3db5f9b8-5f6a-482c-a732-a99a5265de91
(In reply to Karl Mernagh from comment #14) > Here are a few more crash reports. It is the plugin container that stops > working with LastPass. Logging off Lastpass using the icon in the browser or > killing the plugin container in task manager brings FX back to life )I must > restor all tabs if I kill plugin container). See crashes below; I hope they > are related: > > bp-e8a55e72-aab0-4f24-87a5-ba0bb2150730 > bp-b3494edb-92aa-450c-b4f5-3e1282150724 > bp-81039be9-07d6-4fd4-ae01-5d8992150723 > 3db5f9b8-5f6a-482c-a732-a99a5265de91 Hey Karl, so just so we know, LastPass is required in order to hit this crash, and disabling LastPass makes this crash go away?
Hi Mike, That's right. I haven't encountered this with any other addons. Disabling it or even just logging out of lastpass (which I suppose stop it from trying to fill uname and pword fields) stops the crashes. I did encounter this with FF 39 x86 nightly for a period of time but it resolved itself in the x86 version. The x64 still seems to have this. Kind Regards Karl
:ted suggested cc'ing dmajor on this one for crash analysis.
These crash reports suffer from the same reporting problem as in bug 1186092 which is why they appear to be all over the place. The more relevant bits are in the "-upload_file_minidump_browser.dmp" files. I found these strings on the stack but I'm not sure how useful they are: 00000047`34d3e7e8 00007ffa`7f098018 "ipc_channel_error" 00000047`34d3e810 00000047`34d3e830 "browser" 00000047`34d3e900 "(msgtype=0x3A00A1,name=???) Mess" 00000047`34d3e920 "age not allowed: cannot be sent/" 00000047`34d3e940 "recvd in this state" I don't speak IPC very well, maybe Bill can help better.
(In reply to David Major [:dmajor] from comment #18) > These crash reports suffer from the same reporting problem as in bug 1186092 > which is why they appear to be all over the place. The more relevant bits > are in the "-upload_file_minidump_browser.dmp" files. > > I found these strings on the stack but I'm not sure how useful they are: > 00000047`34d3e7e8 00007ffa`7f098018 "ipc_channel_error" > 00000047`34d3e810 00000047`34d3e830 "browser" > 00000047`34d3e900 "(msgtype=0x3A00A1,name=???) Mess" > 00000047`34d3e920 "age not allowed: cannot be sent/" > 00000047`34d3e940 "recvd in this state" The error being reported here is essentially a CPOW timeout. I guess that's not unexpected with LastPass. It uses a ton of CPOWs. Karl, you might try the beta version of LastPass, which is more compatible with e10s. You can find it here: https://rodan.lastpass.com/dev/lp_e10s.xpi (Just for your information, David, you can find this data more easily by clicking on the "Metadata" section of the crash. It's under "ipc_channel_error".)
Thanks Bill, The beta version works perfectly. It looks and feels very much like LastPass for Google Chrome. I've tested it on multiple sites that would crash on me in the past or that would cause the browser to become unresponsive and they all work seamlessly. Thanks again. Karl
Hi Bill, Had all tab crashes again with LastPass disabled on nightly 42. You might be interested in the crash logs https://crash-stats.mozilla.com/report/index/bp-5bb5a325-e000-4e8d-8e3f-492572150807 https://crash-stats.mozilla.com/report/index/bp-449cab44-55a8-439b-bec3-1f7ac2150807 Kind Regards Karl
> https://crash-stats.mozilla.com/report/index/bp-5bb5a325-e000-4e8d-8e3f-492572150807 > https://crash-stats.mozilla.com/report/index/bp-449cab44-55a8-439b-bec3-1f7ac2150807 It has been a bad week for Nightly. There is an issue starting in the August 5 build that causes a bunch of JS GC crashes of varying signatures (bug 1191465 and many duplicates). Most likely you're running into that.
Here is another crash with e10s enabled and Lastpass disabled. Hope it helps https://crash-stats.mozilla.com/report/index/bp-61acbb48-aca2-4242-b2c8-3fcce2150810
There was a bit of back-and-forth on bug 1191465. I expect it will be fixed in the next nightly.
(In reply to dmajor (away) from comment #24) > There was a bit of back-and-forth on bug 1191465. I expect it will be fixed > in the next nightly. Karl, do you agree it is gone?
See Also: → bug 1136983
Unfortunately I can't reproduce the original crash when following the steps from the Description (used the 64 bit Nightly build with the following BuilD ID: 20150713030204 on Windows 10). Karl, do you have any updates on this?
Hi Simona, Sorry for the late reply. The problem seems to be fixed in the latest nightly 64 bit build. Thanks for looking into this.
Based on Comment 27, setting the status of this issue to Resolved Worksforme. Karl, please fell free to Reopen it if the crashes are back on the latest Firefox versions. Thanks!
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.