1092042 - Crash [@ eglsubAndroid.so@0x49b1]

Status: RESOLVED WORKSFORME

(Core :: Graphics, defect)

Description

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

This bug was filed from the Socorro interface and is 
report bp-9f5dccde-7a25-48e3-9e9c-b32692141031.
=============================================================

So I was playing around in Firefox 34 beta on site http://singapore news.github.io/ just selecting different words on the graph on the site, zooming in and out, and this is where I crashed in graphics.

Jeff, do you happen to know how to move on from here? The interesting crashing thread is thread 12 on the crash stack in breakpad.

Comment 1

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

If it matters, I'm on CyanogenMod 11 M11 on a Nexus 5, which is based on Android Kitkat 4.4.4.

Comment 2

[Kelsey Gilbert [:jgilbert]]

AlphaBoxBlur and the blame there points to Bas. Over to him!

Comment 3

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Thanks for moving this bug on, Jeff!

Comment 4

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Not sure if this is related to bug 1067018 or bug 1028802.

Comment 5

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

I'm on Firefox 34 beta build 4 and I think the 2 bugs I referenced were fixed in earlier beta builds of Firefox 34.

Comment 6

[Jonathan Watt [:jwatt]]

Gary, where does the "AlphaBoxBlur::Blur" come from? I see no mention of than in the crash that you linked to. Did you paste the wrong crash ID?

Comment 7

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Click on show/hide other threads; it's on thread 12.

Comment 8

[Jonathan Watt [:jwatt]]

That's not the crashing thread though, so I'm not sure why you've filed this as a crash at mozilla::gfx::AlphaBoxBlur::Blur.

mozilla::gfx::AlphaBoxBlur::Blur is a very expensive function and as such a lot of cycles can be spent in it when it is called. That just means that it's more likely to be at the top of the stack on its thread at any point in time that a _different_ and unrelated thread crashes.

Comment 9

[Bas Schouten (:bas.schouten)]

(In reply to Jonathan Watt [:jwatt] from comment #8)
> That's not the crashing thread though, so I'm not sure why you've filed this
> as a crash at mozilla::gfx::AlphaBoxBlur::Blur.
> 
> mozilla::gfx::AlphaBoxBlur::Blur is a very expensive function and as such a
> lot of cycles can be spent in it when it is called. That just means that
> it's more likely to be at the top of the stack on its thread at any point in
> time that a _different_ and unrelated thread crashes.

Agreed. Thanks for this Jwatt.

Comment 10

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Alright, so I'm now unclear as to what next to do. Is this a crash that Firefox cannot avoid?

Or rather, what can we do to not make Firefox for Android crash?

Comment 11

[Kelsey Gilbert [:jgilbert]]

(In reply to Gary Kwong [:gkw] [:nth10sd] GMT+8 after Oct 9 from comment #10)
> Alright, so I'm now unclear as to what next to do. Is this a crash that
> Firefox cannot avoid?
> 
> Or rather, what can we do to not make Firefox for Android crash?

From the crash it looks like it's in the GPU driver. We need to know what's causing it to crash. MOZ_GL_DEBUG_VERBOSE=1 could help with this.

Comment 12

[Jonathan Watt [:jwatt]]

There are only two crash reports at this location in eglsubAndroid.so in the last 7 days:

https://crash-stats.mozilla.com/report/list?product=FennecAndroid&signature=eglsubAndroid.so%400x49b1

so this wouldn't be our highest priority crash. That said if MOZ_GL_DEBUG_VERBOSE=1 can help identify what's going on here it may be possible to fix this without too much effort.

There are a good number of crashes at other locations in eglsubAndroid.so, (237 at eglsubAndroid.so@0x24ad currently):

https://crash-stats.mozilla.com/query/?product=FennecAndroid&version=ALL%3AALL&query_search=signature&query_type=contains&query=eglsubAndroid.so

Comment 13

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Attachment: example adb logcat

I ran:

MOZ_GL_DEBUG_VERBOSE=1 am start -a android.intent.action.VIEW -n org.mozilla.firefox_beta/.App

from Firefox 34 Beta off Google Play and this produced part of the log in the attachment (it didn't crash yet, they're just sample lines). Will this not work?

Do I have to compile a debug build myself? Or do I need to download a nightly from nightly.mozilla.org?

I ask this because it is difficult to reproduce the crash and I would like to ensure I have the right conditions in place just in case it happens.

Comment 14

[Kelsey Gilbert [:jgilbert]]

(In reply to Gary Kwong [:gkw] [:nth10sd] GMT+8 after Oct 9 from comment #13)
> Created attachment 8515236 [details]
> example adb logcat
> 
> I ran:
> 
> MOZ_GL_DEBUG_VERBOSE=1 am start -a android.intent.action.VIEW -n
> org.mozilla.firefox_beta/.App
> 
> from Firefox 34 Beta off Google Play and this produced part of the log in
> the attachment (it didn't crash yet, they're just sample lines). Will this
> not work?
> 
> Do I have to compile a debug build myself? Or do I need to download a
> nightly from nightly.mozilla.org?
> 
> I ask this because it is difficult to reproduce the crash and I would like
> to ensure I have the right conditions in place just in case it happens.

You need a debug build.

Comment 15

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

I no longer have this operating system on the phone, and haven't seen it since.