Open
Bug 1247249
Opened 5 years ago
Updated 3 years ago
crash in nsThread::ProcessNextEvent | NS_ProcessNextEvent | mozilla::ipc::MessagePump::Run
Categories
(Core :: Plug-ins, defect, P4)
Tracking
()
People
(Reporter: vtamas, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug was filed from the Socorro interface and is report bp-3d44fe2f-a258-473e-9cfd-226992160210. ============================================================= [Affected versions]: Firefox 44 build 3 Firefox 45 beta 3 Firefox 46.0a2 (2016-02-09) Firefox 47.0a1 (2016-02-09) [Affected platforms]: Ubuntu 12.02 64-bit [Steps to reproduce]: 1.Launch Firefox with e10s experiment enabled (multi-process Firefox A/B Test 45.1) 2.Navigate to http://demos.telerik.com/silverlight/#PdfViewer/Thumbnails 3.Wait until the page is loaded. 4.Hit F5 keyboard button. 5.Wait again until the page is loaded. 6.Click on "Reload current page" button from location bar. [Actual results]: Silverlight plugin crashes. [More reports]: bp-6837f758-b63b-4657-ab71-c0f172160210 bp-a80b0604-a0e9-4065-a45a-278b42160210 bp-7fbd7cd7-48b2-4c71-a427-d479b2160210 bp-a51ab44d-394a-4ac8-a5d4-b636b2160210 [Additional notes]: - This crash might be similar to Bug 1243309 - I was unable to reproduce this crash on Firefox 46.0a2 (2016-02-09) and Firefox 44 Rc build 3 (I only encountered Bug 1243309). But, based on Breakdown of total crashes per product and version list, I see that Firefox 46.0a2 and Firefox 44 are affected too. - File: libpipelight-silverlight5.1.so Path: /usr/lib/pipelight/libpipelight-silverlight5.1.so Version: 5.1.40416.0
Comment 1•5 years ago
|
||
Is this a Firefox crash, or is it just the plugin that goes down? The crash reports are a bit all over the place. A plugin shouldn't be able to crash Firefox, but we're unlikely to investigate if the plugin itself is crashing.
Component: Silverlight (Microsoft) → Plug-ins
Flags: needinfo?(vasilica.mihasca)
Product: Plugins → Core
| Reporter | ||
Comment 2•5 years ago
|
||
(In reply to Benjamin Smedberg [:bsmedberg] from comment #1) > Is this a Firefox crash, or is it just the plugin that goes down? The crash > reports are a bit all over the place. A plugin shouldn't be able to crash > Firefox, but we're unlikely to investigate if the plugin itself is crashing. This is a Firefox Crash.
Flags: needinfo?(vasilica.mihasca)
Comment 3•5 years ago
|
||
It is reproducible in aurora when multi-process(e10s)is enabled. If e10s is disabled,the page does not crash. Crash reports: bp-f0b33878-458d-4f5f-93eb-c61432160302 bp-86996bd6-c3a9-4fee-9ca8-4d0c22160302 bp-98a356a8-0075-4eb9-ad32-b75592160302 Regression range: Last good revision: a019592053c4d93fbbafab8d0bd709529e3746de First bad revision: 7308dd0a6c3b7049dbd8346c7f435c5e03500b65 Pushlog: https://hg.mozilla.org/releases/mozilla-aurora/pushloghtml?fromchange=a019592053c4d93fbbafab8d0bd709529e3746de&tochange=7308dd0a6c3b7049dbd8346c7f435c5e03500b65 Suspect: a402fa89a728— Bug 1188605 - Turn e10s on by default for Aurora.
Comment 4•5 years ago
|
||
Platform: Ubuntu 14.04, x86_64
Updated•5 years ago
|
tracking-e10s:
--- → ?
Updated•5 years ago
|
Priority: -- → P4
Crash volume for signature 'nsThread::ProcessNextEvent | NS_ProcessNextEvent | mozilla::ipc::MessagePump::Run':
- nightly (version 50): 2 crashes from 2016-06-06.
- aurora (version 49): 3 crashes from 2016-06-07.
- beta (version 48): 33 crashes from 2016-06-06.
- release (version 47): 108 crashes from 2016-05-31.
- esr (version 45): 8 crashes from 2016-04-07.
Crash volume on the last weeks:
W. N-1 W. N-2 W. N-3 W. N-4 W. N-5 W. N-6 W. N-7
- nightly 0 0 0 1 1 0 0
- aurora 0 0 0 2 0 1 0
- beta 8 2 5 7 3 3 3
- release 27 12 13 10 14 13 9
- esr 1 0 0 1 1 2 2
Affected platforms: Windows, Linux
status-firefox48:
--- → affected
status-firefox49:
--- → affected
status-firefox50:
--- → affected
status-firefox-esr45:
--- → affected
Updated•3 years ago
|
Crash Signature: [@ nsThread::ProcessNextEvent | NS_ProcessNextEvent | mozilla::ipc::MessagePump::Run] → [@ nsThread::ProcessNextEvent | NS_ProcessNextEvent | mozilla::ipc::MessagePump::Run]
[@ mozilla::ipc::MessagePump::Run ]
You need to log in
before you can comment on or make changes to this bug.
Description
•