1154197 - [E10s] Browsing stops more than a minute with waiting sign

Status: RESOLVED INVALID

(Core :: DOM: Content Processes, defect)

Description

[Kami]

Attachment: endlesswaiting.png

With the recent build of Nigthly I hit a problem. The browsing stops more than one minute with waiting sign. I opened lots of tabs (actually more than 200) and it worked well but suddenly some of the tabs won't load again. Opening a non E10s windows still works well so this could be related only to E10s.

Version 	40.0a1
Build ID 	20150413030203

Multiprocess Windows 	3/3 (default: true)

Adapter Description	AMD Radeon HD 6350
Adapter Drivers	aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64
Adapter RAM	512
Asynchronous Pan/Zoom	none
Device ID	0x68f9
Direct2D Enabled	true
DirectWrite Enabled	true (6.2.9200.16492)
Driver Date	3-19-2015
Driver Version	14.502.1014.0
GPU #2 Active	false
GPU Accelerated Windows	3/3 Direct3D 11 (OMTC)
Subsys ID	2126103c
Vendor ID	0x1002
WebGL Renderer	Google Inc. -- ANGLE (AMD Radeon HD 6350 Direct3D11 vs_5_0 ps_5_0)
windowLayerManagerRemote	true
AzureCanvasBackend	direct2d 1.1
AzureContentBackend	direct2d 1.1
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0

Windows 7 64 bit

Comment 1

[Tracy Walker [:tracy]]

Kami, can you retry will all of your addons disabled

Comment 2

[Kami]

Only Buffer and uBlock was enable. now i disable them and keep trying.

Comment 3

[Kami]

Without extension it happened again. but I am not sure the situation is same because finally it crashed all the tabs.

I saw these in about:crashes:
bp-78f206ec-fcd3-4ded-8992-97f0a2150507
	2015.05.07.	16:28
589849b8-4640-4056-89d2-1152a34a5743
	2015.05.07.	16:26

Comment 4

[Tracy Walker [:tracy]]

that's an Out Of Memory crash: [@ OOM | unknown | mozalloc_abort(char const* const) | mozalloc_handle_oom(unsigned int) | moz_xmalloc | CCGraphBuilder::NoteXPCOMChild(nsISupports*) ]

Comment 5

[Brad Lassey [:blassey] (use needinfo?)]

So this bug (the browser stopping for a minute) seems to be an issue with one of your addons. If you can determine which one it could be helpful for the addon developer.

The crash is unrelated, please file another bug for it.

Comment 6

[:shell escalante]

Let us know if you need this re-opened.  sounds like there was a crasher bug and then add-ons, but no details on which add-on may have caused related issue.... so we don't really know where to go with it.

Comment 7

[Kami]

Cannot reproduce it anymore