1096103 - [E10S] Lockup navigating to a page while page is loading, with LastPass

Status: RESOLVED WORKSFORME

(Core :: General, defect)

Description

[Ryan Jones-Ward [:sciguyryan]]

With E10S enabled in the nightly build for 11-08-14 the following reliably causes a lockup.

The only way to correct this is to either forcibly kill the browser instance or the content process.

Step 1. Go to the following location: http://minecraft.curseforge.com/mc-mods/224218-compact-machines
Step 2. While the page is still loading click the "Projects" link.
Step 3. The browser should lock up completely.

This does not seem to occur at all if the page is allowed to fully load before performing the above steps. This also did not occur before E10S was enabled.

Unfortunately as it is not a crash I don't have any logs to provide here. However if there is any means of obtaining usable data that I can try, please let me know.

Comment 1

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

Seems like a problem in input.mozilla.org.

Comment 2

[Will Kahn-Greene [:willkg] ET needinfo? me]

Bill: I'm a little confused. Can you walk me through what this has to do with Input?

Comment 3

[David Parks [:handyman]]

(In reply to Ryan Jones from comment #0)
> With E10S enabled in the nightly build for 11-08-14 the following reliably
> causes a lockup.
...
> Unfortunately as it is not a crash I don't have any logs to provide here.
> However if there is any means of obtaining usable data that I can try,
> please let me know.

Hi Ryan.  We aren't sure what may have happened but it looks like it might be a known plugin issue.  If so, there is a good chance it was fixed since 11-08.  Would you mind checking the latest nightly to see if you still have the problem?

If that doesn't work for you, can you let me know what addons/plugins you are using?  Also, what type of machine/OS you are running (or you can just copy-paste your Troubleshooting Information from the Firefox 'About' window).

Comment 4

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

Sorry, posted in the wrong bug.

Comment 5

[Ryan Jones-Ward [:sciguyryan]]

(In reply to David Parks [:handyman] from comment #3)
> (In reply to Ryan Jones from comment #0)
> > With E10S enabled in the nightly build for 11-08-14 the following reliably
> > causes a lockup.
> ...
> > Unfortunately as it is not a crash I don't have any logs to provide here.
> > However if there is any means of obtaining usable data that I can try,
> > please let me know.
> 
> Hi Ryan.  We aren't sure what may have happened but it looks like it might
> be a known plugin issue.  If so, there is a good chance it was fixed since
> 11-08.  Would you mind checking the latest nightly to see if you still have
> the problem?
> 
> If that doesn't work for you, can you let me know what addons/plugins you
> are using?  Also, what type of machine/OS you are running (or you can just
> copy-paste your Troubleshooting Information from the Firefox 'About' window).

I'm actually currently using the 8/11 build at present and the issue is still present.

As requested here is the relevant information from about:support. I have trimmed some of the stuff out (like crashes) since I don't believe they are relevant and they make it much larger.

--------------------------------------------------

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

Name: Firefox
Version: 36.0a1
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0
Multiprocess Windows: 1/1

Extensions
----------

Name: ADB Helper
Version: 0.7.1
Enabled: true
ID: [e-mail]

Name: Adblock Plus
Version: 2.6.5
Enabled: true
ID: {d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}

Name: British English Dictionary
Version: 1.19.1
Enabled: true
ID: [e-mail]

Name: Disable Anti-Adblock
Version: 3.1
Enabled: true
ID: {d49a148e-817e-4025-bee3-5d541376de3b}

Name: LastPass
Version: 3.1.54
Enabled: true
ID: [e-mail]

Name: printpdf
Version: 0.76
Enabled: true
ID: [e-mail]

Name: Update Channel Selector
Version: 1.6.1
Enabled: true
ID: [e-mail]

Name: Xmarks
Version: 4.3.5
Enabled: true
ID: [e-mail]

Name: Disconnect
Version: 3.14.0
Enabled: false
ID: [e-mail]

Name: DNS Flusher
Version: 3.1.1
Enabled: false
ID: {7d575baa-b543-11dc-8314-0800200c9a66}

Name: DownloadHelper
Version: 4.9.24
Enabled: false
ID: {b9db16a4-6edc-47ec-a1f4-b86292ed211d}

Name: Firebug
Version: 2.0.6
Enabled: false
ID: [e-mail]

Graphics
--------

Adapter Description: NVIDIA GeForce GTX 780
Adapter Drivers: nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Adapter RAM: 3072
Device ID: 0x1004
Direct2D Enabled: true
DirectWrite Enabled: true (6.2.9200.16571)
Driver Date: 11-3-2014
Driver Version: 9.18.13.4465
GPU #2 Active: false
GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC)
Subsys ID: 104b10de
Vendor ID: 0x10de
WebGL Renderer: Google Inc. -- ANGLE (NVIDIA GeForce GTX 780 Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote: true
AzureCanvasBackend: direct2d
AzureContentBackend: direct2d 1.1
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0

JavaScript
----------

Incremental GC: true

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

Activated: false
Prevent Accessibility: 0

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

NSPR
Expected minimum version: 4.10.7
Version in use: 4.10.7

NSS
Expected minimum version: 3.18 Basic ECC Beta
Version in use: 3.18 Basic ECC Beta

NSSSMIME
Expected minimum version: 3.18 Basic ECC Beta
Version in use: 3.18 Basic ECC Beta

NSSSSL
Expected minimum version: 3.18 Basic ECC Beta
Version in use: 3.18 Basic ECC Beta

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

--------------------------------------------------


If you need anything else just let me know.

Comment 6

[David Parks [:handyman]]

(In reply to Ryan Jones from comment #5)
> I'm actually currently using the 8/11 build at present and the issue is
> still present.

I take it that's a typo and you are on the 11/11 build, which means I've got some work to do.  I'd hoped that recent windows plugin work would have cleared this up but no luck.  Many thanks for the help.

Comment 7

[Ryan Jones-Ward [:sciguyryan]]

(In reply to David Parks [:handyman] from comment #6)
> (In reply to Ryan Jones from comment #5)
> > I'm actually currently using the 8/11 build at present and the issue is
> > still present.
> 
> I take it that's a typo and you are on the 11/11 build, which means I've got
> some work to do.  I'd hoped that recent windows plugin work would have
> cleared this up but no luck.  Many thanks for the help.

Yes, sorry. 11/11 as is shown by my US string in the post.

If you need any further information just let me know. I'll keep an eye on the bug in case.

Thanks for investigating!

Comment 8

[Will Kahn-Greene [:willkg] ET needinfo? me]

Switching this back to the original product.

Comment 9

[David Parks [:handyman]]

Hey Will, would you mind retrying this with your addons disabled?  e10s has some issues with some addons (esp. heavy-duty like LastPass) so this might help to track down the culprit.  Thanks

Comment 10

[Ryan Jones-Ward [:sciguyryan]]

(In reply to David Parks [:handyman] from comment #9)
> Hey Will, would you mind retrying this with your addons disabled?  e10s has
> some issues with some addons (esp. heavy-duty like LastPass) so this might
> help to track down the culprit.  Thanks

Given how randomly the error occurs I can try but I make no guarantees of pinning it down. I've already tried this several times with no conclusive results.

I tested it with several of the addons turned off and sometimes it occurred, sometimes it did - even with the same combinations of mods.

I'll keep looking and report back if I can narrow it down. My current addon list is included in this bug report already if anyone else is able to test it too.

Comment 11

[Ryan Jones-Ward [:sciguyryan]]

After doing some more testing it seems like it is LostPass.

I went through 4 hours of general browsing with it disabled and no lockups. 3 lockups in that time since turning it back on.

While I cannot conclusively say it wouldn't occurred without it enabled it seems quite likely that it is in some way involved.

It's also pretty bad since I have to manually kill the whole content process, effectively crashing all of the open tabs in order to correct it.

Comment 12

[David Parks [:handyman]]

That narrows it down a lot.  Should be enough to get started.  Thanks Ryan.

Comment 13

[:shell escalante]

engaging with author to see when version 4 which is e10s compatible will move from Beta to release

Comment 14

[Andrei Purice]

Following the reporter's steps I am able to confirm that the issues doesn't happen anymore on Windows 10 on any of the current versions of Firefox Nightly 87.0a1 (2021-02-22), beta 86.0 and release 85.0.2. No crashes occur under the given test case.

Closing this issue as Resolved > Worksforme.
Feel free to re-open or file a new bug if this issue reoccurs again.