878542 - crash in liboemcamera.so@0x12240 on Keon / [@ liboemcamera.so@0x12494 ] on inari

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect)

Description

[Scoobidiver (away)]

It's #6 top crasher in B2G 18.0. Crashes occurs in B2G 18.0/20130527 on Keon.

Here is a crash report: bp-7efa3a4a-4fc3-4588-a565-c791e2130601.

Frame 	Module 	Signature 	Source
0 	liboemcamera.so 	liboemcamera.so@0x12240 	
1 	liboemcamera.so 	liboemcamera.so@0x6b42e

More reports at:
https://crash-stats.mozilla.com/report/list?signature=liboemcamera.so%400x12240

Comment 1

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I think https://crash-stats.mozilla.com/report/index/ef57c05c-9efb-43bc-bc78-436732130729 on inari might be the same issue?

Not sure if it's a driver issue or something in the system as of yet...

Comment 2

[Scoobidiver (away)]

(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #1)
> I think
> https://crash-stats.mozilla.com/report/index/ef57c05c-9efb-43bc-bc78-
> 436732130729 on inari might be the same issue?
I think so.

Comment 3

[Scoobidiver (away)]

Adding the ZTE version.

Comment 4

[Scoobidiver (away)]

It's #1 top crasher in FxOS 1.0.1.

Comment 5

[Robert Kaiser]

(In reply to Scoobidiver from comment #4)
> It's #1 top crasher in FxOS 1.0.1.

Yes, this has clearly been dominating the lists, see e.g. https://crash-analysis.mozilla.com/rkaiser/2013-07-31/2013-07-31.b2g.topcrashes.weekly.html#b2g-1.0.1.0-prerelease

Comment 6

[Mike Habicher [:mikeh] (high bugzilla latency)]

I looked quickly through the crash reports, and all of the stack traces were the same and not useful. We're require ZTE's help here in turning report addresses into crash-reasons.

Comment 7

[Robert Kaiser]

Yes, we know that stackwalking doesn't work well where we don't have symbols, i.e. in this case, for example. IIRC, bsmedberg is working on improving that in the future. That said, for this current crash, I agree that we need ZTE to look into this.

Comment 8

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Hi Ivan, would it be possible for you to ask ZTE to look into this bug please?  This is one of the top crashers in the 1.0.1 release.

Comment 9

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Not sure, but I may have figured either this crash or bug 901226:

STR:
1. launch camera app
2. hold the phone in landscape mode
3. keep taking pictures at different angles.

Trying to find out the duplicate report issues still

Comment 10

[Ivan Tsay (:ITsay)]

Sent the request to ZTE for them to look at this bug

Comment 11

[Tracy Walker [:tracy]]

topcrash is being replaced by more precise keywords per https://bugzilla.mozilla.org/show_bug.cgi?id=927557#c3

Comment 12

[bhavana bajaj [:bajaj]]

NI on Ivan here as to what the next steps are. Given this is not actionable form our side, unclear if we should be blocking at all on such issues.

Comment 13

[Ivan Tsay (:ITsay)]

Bhavana,

May I know if this issue is still reproduced in v1.1? Form the bug info here, it seems to happen in the 1.0. From my opinion, this one is not a blocker for v1.1 now since we are not sure if it can be reproduced in v1.1. I suggest we can minus this one by now. And renominate this one if it can be reproduced in v1.1. Currently our partner has released the FOTA for 1.0 users in most of the 1.0 released countries. I can also check with our partner for them to take a look this one based on v1.1

Comment 14

[Robert Kaiser]

(In reply to Ivan Tsay (:ITsay) from comment #13)
> Currently our partner has released the FOTA for 1.0
> users in most of the 1.0 released countries.

I disagree in that, we see almost no data coming in for 1.1 at all, but a lot for 1.0.1, so I do not believe that any significant part of devices "in the wild" has actually been updated. (We would at least see some kind of crashes from 1.1 and many fewer from 1.0.1 if they were updated.)

Given that we don't get any decent amount of data from 1.1 at all so far, we cannot know if this happens on that as well - but given that we haven't heard of any fixes being done to this, I'd be surprised if it did not happen on 1.1 as well, actually.

Comment 15

[BMO Automation]

Firefox OS is not being worked on