1189034 - [e10s] Crash after visiting a particular github link

Status: RESOLVED WORKSFORME

(Core :: Graphics, defect)

Description

[Saheda Reza [:Antora]]

Attachment: Crash mesg.JPG

User Agent: Mozilla/5.0 (Windows NT 6.3; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20150729030208

Steps to reproduce:


Go to the link : https://github.com/cgjones/platform-demo-mc/blob/master/gfx/gl/GLContextProviderEGL.cpp




Actual results:

 it showed black screen and after sometime this site caught by crashing message on e10s mode.


Expected results:

There should be no crash.

Comment 1

[[:Towkir] Ahmed]

Looks like you need to scroll till the end of the page sometimes to see the crash, but reproducible each time. Todays nightly is affected.

I am not sure about the component though, e10s had a crash and non-e10s had some graphical issues like texts overlaping or black rectangles or whole black screen.

Comment 2

[Mike Conley (:mconley) (:⚙️)]

Thanks for reporting!

Can you please send us a link to one of your crash reports for this crash? You can find those in about:crashes.

Comment 3

[Saheda Reza [:Antora]]

Last crash report is https://crash-stats.mozilla.com/report/index/eb9ae275-a574-4793-b79f-4d9f82150729

Comment 4

[[:Towkir] Ahmed]

and here is my one https://crash-stats.mozilla.com/report/index/57b218fe-c9d8-401a-a76f-15f072150729

Comment 5

[Mike Conley (:mconley) (:⚙️)]

Hey Towkir, that crash looks separate - looks like it was caused by the Gecko Profiler.

Comment 6

[Mike Conley (:mconley) (:⚙️)]

(In reply to Saheda Reza [:Antora] from comment #3)
> Last crash report is
> https://crash-stats.mozilla.com/report/index/eb9ae275-a574-4793-b79f-
> 4d9f82150729

Hey Antora - are you able to reliably reproduce this? If so, can you post other crash reports? I want to ensure that they're all occurring in "the same place".

Comment 7

[Saheda Reza [:Antora]]

Here are some crash reports form my browser

https://crash-stats.mozilla.com/report/index/eb9ae275-a574-4793-b79f-4d9f82150729
https://crash-stats.mozilla.com/report/index/11d7aba4-8207-4d17-b078-1b3b52150722
https://crash-stats.mozilla.com/report/index/7369549a-f9c3-4c56-924d-2aed72150722
https://crash-stats.mozilla.com/report/index/ed58481e-5b9e-4057-8978-80ff22150722
https://crash-stats.mozilla.com/report/index/bb338817-6428-4c9c-b128-3bc032150711

Comment 8

[Jim Mathies [:jimm]]

Hey Saheda, could you do us a favor - 

1) clear your crash reports in about:crashes
2) wait for the next crash
3) post the crash link and your about:support

thanks!

Comment 9

[[:Towkir] Ahmed]

Jim can you tell us how to manually turn on crash reporter, 
because after removing all crash reports, we faced the crash each time we opened that link and nightly did provide the chance to restore the tabs but not the chance to submit any crash report.
That is why we are having the crashes and could not find the reports at about:crashes
Thanks

Comment 10

[Saheda Reza [:Antora]]

Next crash reports
https://crash-stats.mozilla.com/report/index/084861a7-8c43-48bd-941e-479132150814

Comment 11

[Saheda Reza [:Antora]]

My crash reports on Latest Firefox 43.0a1

Build ID 	20150813030208
User Agent 	Mozilla/5.0 (Windows NT 6.3; rv:43.0) Gecko/20100101 Firefox/43.0

(In reply to Jim Mathies [:jimm] from comment #8)
> Hey Saheda, could you do us a favor - 
> 
> 1) clear your crash reports in about:crashes
> 2) wait for the next crash
> 3) post the crash link and your about:support
> 
> thanks!

Comment 12

[Jim Mathies [:jimm]]

(In reply to Saheda Reza [:Antora] from comment #10)
> Next crash reports
> https://crash-stats.mozilla.com/report/index/084861a7-8c43-48bd-941e-
> 479132150814

This is from an old build of nightly dated 7-7, installed on 7-22. The crash is a stack overflow in css parsing. I don't see any issues with your modules so it doesn't look malware related. There are a few of these types of crashes across multiple versions but they are very rare (70 crashes over the last 7 days across our install base.)

Let's see if we can get a newer crash from your more recent nightly build.

Comment 13

[Jim Mathies [:jimm]]

Also, would you mind posting your about:support so we can take a look at your hardware and settings?

Comment 14

[Saheda Reza [:Antora]]

Here is about support

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

Name: Firefox
Version: 43.0a1
Build ID: 20150819030206
Update Channel: nightly
User Agent: Mozilla/5.0 (Windows NT 6.3; rv:43.0) Gecko/20100101 Firefox/43.0
Multiprocess Windows: 1/1 (default: true)
Safe Mode: false

Crash Reports for the Last 3 Days
---------------------------------

All Crash Reports

Extensions
----------

Name: Adobe Contribute Toolbar
Version: 6.0
Enabled: false
ID: {01A8CA0A-4C96-465b-A49B-65C46FAD54F9}

Graphics
--------

Adapter Description: Intel(R) HD Graphics
Adapter Drivers: igdumdim32 igd10iumd32 igd10iumd32
Adapter RAM: Unknown
Asynchronous Pan/Zoom: wheel input enabled
Device ID: 0x0152
Direct2D Enabled: true
DirectWrite Enabled: true (6.3.9600.17999)
Driver Date: 9-26-2014
Driver Version: 10.18.10.3958
GPU #2 Active: false
GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC)
Subsys ID: 00000000
Supports Hardware H264 Decoding: Yes
Vendor ID: 0x8086
WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics Direct3D11 vs_5_0 ps_5_0)
windowLayerManagerRemote: true
AzureCanvasBackend: direct2d 1.1
AzureContentBackend: direct2d 1.1
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0

Important Modified Preferences
------------------------------

browser.cache.disk.capacity: 1048576
browser.cache.disk.filesystem_reported: 1
browser.cache.disk.smart_size.first_run: false
browser.cache.frecency_experiment: 1
browser.download.importedFromSqlite: true
browser.places.smartBookmarksVersion: 7
browser.startup.homepage_override.buildID: 20150819030206
browser.startup.homepage_override.mstone: 43.0a1
dom.apps.reset-permissions: true
dom.mozApps.used: true
extensions.lastAppVersion: 43.0a1
gfx.crash-guard.d3d11layers.appVersion: 43.0a1
gfx.crash-guard.d3d11layers.deviceID: 0x0152
gfx.crash-guard.d3d11layers.driverVersion: 10.18.10.3958
gfx.crash-guard.d3d11layers.feature-d2d: true
gfx.crash-guard.d3d11layers.feature-d3d11: true
gfx.crash-guard.status.d3d11layers: 2
gfx.crash-guard.status.d3d9video: 2
gfx.direct3d.last_used_feature_level_idx: 0
media.hardware-video-decoding.failed: false
network.cookie.prefsMigrated: true
places.history.expiration.transient_current_max_pages: 50797
plugin.disable_full_page_plugin_for_types: application/pdf
privacy.sanitize.migrateFx3Prefs: true
security.sandbox.content.tempDirSuffix: {c16cbc37-d0b6-445e-998e-234e99b85b95}

Important Locked Preferences
----------------------------

JavaScript
----------

Incremental GC: true

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

Activated: false
Prevent Accessibility: 0

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

NSPR
Expected minimum version: 4.10.9 Beta
Version in use: 4.10.9 Beta

NSS
Expected minimum version: 3.20 Basic ECC
Version in use: 3.20 Basic ECC

NSSSMIME
Expected minimum version: 3.20 Basic ECC
Version in use: 3.20 Basic ECC

NSSSSL
Expected minimum version: 3.20 Basic ECC
Version in use: 3.20 Basic ECC

NSSUTIL
Expected minimum version: 3.20
Version in use: 3.20

Experimental Features
---------------------

Comment 15

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

re-setting NI for comment 12

Comment 16

[Saheda Reza [:Antora]]

A crash with this ID:  a1194c30-7e24-4a4f-9a02-a20605db310d  shows a date time of  8/23/2015 -- 4:08 AM

It says ,'page not found' and another one does the same
I have no newer crash reports except these two
I will provide as soon as i have more

Comment 17

[Jim Mathies [:jimm]]

I tried punching that into crashstats and I get an "Invalid Crash ID" error - 

https://crash-stats.mozilla.com/report/index/a1194c30-7e24-4a4f-9a02-a20605db310d

Would you mind rechecking?

Comment 18

[Saheda Reza [:Antora]]

(In reply to Jim Mathies [:jimm] from comment #17)
> I tried punching that into crashstats and I get an "Invalid Crash ID" error

  That's what I said, It's says 'Page not found' and I had no new/valid crash report.
  Please read carefully comment 16
 
> https://crash-stats.mozilla.com/report/index/a1194c30-7e24-4a4f-9a02-
> a20605db310d
> 
> Would you mind rechecking?
  
  I found some new reports today and here are those :

  https://crash-stats.mozilla.com/report/index/bcbb213f-2e98-44ed-bfcc-c96f62150827
  https://crash-stats.mozilla.com/report/index/ea554691-6ed7-4368-849f-ee3642150827

  Besides I am very disappointed that you did not reply comment 9

Comment 19

[Robert Helmer [:rhelmer]]

(In reply to Saheda Reza [:Antora] from comment #16)
> A crash with this ID:  a1194c30-7e24-4a4f-9a02-a20605db310d  shows a date
> time of  8/23/2015 -- 4:08 AM
> 
> It says ,'page not found' and another one does the same
> I have no newer crash reports except these two
> I will provide as soon as i have more

This ID indicates that the crash was not actually sent to the server - first a crash is generated with a random UUID locally, then when it is submitted to the crash reporting service a crash ID in the form of "bp-{new UUID}YYMMDD" is returned, which overrides the local UUID.

Do you see the ID "a1194c30-7e24-4a4f-9a02-a20605db310d" in the about:crashes UI? Usually these are all upper-case, and clicking on it will display a "loading" spinner and submit the crash to the crash reporting service.

Comment 20

[Robert Helmer [:rhelmer]]

(In reply to [:Towkir] Ahmed from comment #9)
> Jim can you tell us how to manually turn on crash reporter, 
> because after removing all crash reports, we faced the crash each time we


Did you disable the crash reporter? How did you remove reports?


> opened that link and nightly did provide the chance to restore the tabs but
> not the chance to submit any crash report.
> That is why we are having the crashes and could not find the reports at
> about:crashes
> Thanks

The in-browser "about:crashes" UI allows you to see your local crashes, and submit them if the standalone crash client was unable to for some reason (unsubmitted crashes are all upper-case and do not have the prefix "bp-").

Some crashes are not caught by Firefox's crash reporter, so if you still don't see them then this is a possible reason.

Comment 21

[Robert Helmer [:rhelmer]]

(In reply to Robert Helmer [:rhelmer] from comment #20)
> (In reply to [:Towkir] Ahmed from comment #9)
> > Jim can you tell us how to manually turn on crash reporter, 
> > because after removing all crash reports, we faced the crash each time we
> 
> 
> Did you disable the crash reporter? How did you remove reports?

Ah comment 8, I see. That should not have disabled the crash reporter.

Comment 22

[[:Towkir] Ahmed]

(In reply to Robert Helmer [:rhelmer] from comment #19)
> (In reply to Saheda Reza [:Antora] from comment #16)
> > A crash with this ID:  a1194c30-7e24-4a4f-9a02-a20605db310d  shows a date
> > time of  8/23/2015 -- 4:08 AM
> > 
> > It says ,'page not found' and another one does the same
> > I have no newer crash reports except these two
> > I will provide as soon as i have more
> 
> This ID indicates that the crash was not actually sent to the server - first
> a crash is generated with a random UUID locally, then when it is submitted
> to the crash reporting service a crash ID in the form of "bp-{new
> UUID}YYMMDD" is returned, which overrides the local UUID.

  With that, I could know how crash reports works, thanks for that.

> Do you see the ID "a1194c30-7e24-4a4f-9a02-a20605db310d" in the
> about:crashes UI? Usually these are all upper-case, and clicking on it will
> display a "loading" spinner and submit the crash to the crash reporting
> service.
  Yes, the id is always like that, I am attaching a screenshot of my most recent crashes and the UI of about:crashes

Comment 23

[[:Towkir] Ahmed]

Attachment: about_crashesUI.png

screenshot for comment 22

Comment 24

[[:Towkir] Ahmed]

(In reply to Robert Helmer [:rhelmer] from comment #20)
> (In reply to [:Towkir] Ahmed from comment #9)
> > Jim can you tell us how to manually turn on crash reporter, 
> > because after removing all crash reports, we faced the crash each time we
> 
> 
> Did you disable the crash reporter? How did you remove reports?
 
 Nope, actually I was looking for a way to submit my reports with that reporter, because after the crash I had the new "Bad news first" message of nightly e10s. which did not turn on the crash reporter but only restarted firefox with my lost tabs, but afaik  usual crash was just closing firefox and opening the reporter.
  
> > opened that link and nightly did provide the chance to restore the tabs but
> > not the chance to submit any crash report.
> > That is why we are having the crashes and could not find the reports at
> > about:crashes
> > Thanks
> 
> The in-browser "about:crashes" UI allows you to see your local crashes, and
> submit them if the standalone crash client was unable to for some reason
> (unsubmitted crashes are all upper-case and do not have the prefix "bp-").
 You can see the screenshot and I am attaching the latest crash links which all three happened after visiting this specific github page link : 
https://github.com/cgjones/platform-demo-mc/blob/master/gfx/gl/GLContextProviderEGL.cpp
before the crash, there were some text scramble on that page and the crash happened, you can try visiting that link.


here are the crashes, I hope the reason of them are visiting that page
https://crash-stats.mozilla.com/report/index/33131afa-f275-4427-ba54-cc55a2150827
https://crash-stats.mozilla.com/report/index/58e1e25d-216d-4856-a8a3-05e7c2150827
https://crash-stats.mozilla.com/report/index/85b98e8a-e7ca-48e2-b9b2-4ac7f2150827
https://crash-stats.mozilla.com/report/index/7bfe44ec-ab26-49ce-a389-48bbf2150827


and yes, the way I removed the reports was clicking the red marked button on the screenshot "Remove all reports"

The text scrambling screenshot is going to be attached

Thanks

Comment 25

[[:Towkir] Ahmed]

Attachment: textScrambleBeforeCrash.png

Wile visiting that page, after a little scrolling down, the source codes get scrambled like this screenshot.

Please visit that github link and see what happens on your browser.
Thanks :)

Comment 26

[Jim Mathies [:jimm]]

(In reply to [:Towkir] Ahmed from comment #9)
> Jim can you tell us how to manually turn on crash reporter, 
> because after removing all crash reports, we faced the crash each time we
> opened that link and nightly did provide the chance to restore the tabs but
> not the chance to submit any crash report.
> That is why we are having the crashes and could not find the reports at
> about:crashes
> Thanks

It's on by default in release builds. You can't turn it off. Possibly there's bug in crash submittal?

Comment 27

[Jim Mathies [:jimm]]

> here are the crashes, I hope the reason of them are visiting that page
> https://crash-stats.mozilla.com/report/index/33131afa-f275-4427-ba54-
> cc55a2150827
> https://crash-stats.mozilla.com/report/index/58e1e25d-216d-4856-a8a3-
> 05e7c2150827
> https://crash-stats.mozilla.com/report/index/85b98e8a-e7ca-48e2-b9b2-
> 4ac7f2150827
> https://crash-stats.mozilla.com/report/index/7bfe44ec-ab26-49ce-a389-
> 48bbf2150827

These are gfx related.

Comment 28

[[:Towkir] Ahmed]

thanks jim, at least we could know the reason. are those two from comment 18 also gfx related?

Comment 29

[Jim Mathies [:jimm]]

(In reply to [:Towkir] Ahmed from comment #28)
> thanks jim, at least we could know the reason. are those two from comment 18
> also gfx related?

Those appear to be completely different - they appear to be related to a profiling feature that landed about a month ago in bug 1183229. Basically I think you two have reported two different bugs, so we should probably split the two up.

Comment 30

[George Wright (:gw280) (needinfo me!)]

I am unable to reproduce this at all on my win8.1/intel gfx machine. Are you still able to reproduce this?

Comment 31

[Saheda Reza [:Antora]]

I just tried with a fresh profile with updated nightly Version 44.0a1

it is all the same as it was. crashing again :-(

Comment 32

[George Wright (:gw280) (needinfo me!)]

Can you post your current about:crash links?

Comment 33

[George Wright (:gw280) (needinfo me!)]

Milan, do you have any hardware in the gfx lab that matches this?

Comment 34

[Milan Sreckovic [:milan] (needinfo for best results)]

Probably: https://wiki.mozilla.org/QA/Platform/Graphics/Inventory

Comment 35

[Saheda Reza [:Antora]]

it is all the same as it was, Nightly Version 44.0a1

Build ID 	20151008030232
User Agent 	Mozilla/5.0 (Windows NT 6.3; rv:44.0) Gecko/20100101 Firefox/44.0

Crash report
https://crash-stats.mozilla.com/report/index/bp-1a599625-bc8b-4e54-aa63-5a3f82151009
https://crash-stats.mozilla.com/report/index/bp-17867711-4d1d-4cea-813b-a0edc2151009

Comment 36

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

Needinfo George to try with the same driver version.

Comment 37

[George Wright (:gw280) (needinfo me!)]

I installed the 10.18.10.3958 driver from Intel and still can't reproduce this. Saheda, can you give more details of your machine? In particular, which Intel CPU/GPU model do you have, and are you running 32-bit Windows?

Comment 38

[George Wright (:gw280) (needinfo me!)]

Another thing you may want to try is upgrading your drivers to the latest ones provided by intel (the ones you have are quite old at this point) and seeing if that resolves this crash.

Comment 39

[Saheda Reza [:Antora]]

I have upgraded drivers and that fixed this issue.
thanks everyone