[Sora][Browser]there have crash in browser when I reenter it after pressing home key to exit it

NEW
Unassigned

Status

Firefox OS
Gaia::Browser
P1
normal
4 years ago
2 years ago

People

(Reporter: sync-1, Unassigned)

Tracking

(Blocks: 1 bug, {crash})

unspecified
crash

Firefox Tracking Flags

(blocking-b2g:-)

Details

(Whiteboard: [b2g-crash], crash signature)

Attachments

(2 attachments)

4.24 MB, application/x-rar-compressed
Details
64.35 KB, text/plain
Details
(Reporter)

Description

4 years ago
Mozilla build ID:20140422024003
 
 DEFECT DESCRIPTION:  
 there have crash in browser when I reenter it after pressing home key to exit it 
 REPRODUCING PROCEDURES:
 1.lanuch "http://imps.tcl-ta.com/cailiang/media/alca_wbmp.html" ,choose "basket " to open
 2.press home key to exit  the browser 
 3.do someting ,such as going to setting,calling etc. 
 4.click browser to open it 
 5.it will not show the crash interface --->KO1
 
 EXPECTED BEHAVIOUR:
 KO1:the picture display normally,and no crash
 ASSOCIATE SPECIFICATION:
 TEST PLAN REFERENCE:
 TOOLS AND PLATFORMS USED:
 USER IMPACT:
 REPRODUCING RATE:
 5/5 
 For FT PR, Please list reference mobile's behavior:
 If the bug is not clear, please call me
(Reporter)

Comment 1

4 years ago
Created attachment 8431451 [details]
log and picture
Crash Signature: [@ PR_Lock | imgFrame::ImageUpdated(nsIntRect const&) ]
Keywords: crash
Whiteboard: [b2g-crash]

Comment 3

3 years ago
[Blocking Requested - why for this release]:
blocking-b2g: --- → 2.0?

Comment 4

3 years ago
This can reproduce on FFOS2.0.
Hi TCL, ChengLin:

I can't repro. with Flame v188 (2.0) SW. would you clarify more about the STR?

 3.do someting ,such as going to setting,calling etc. 
--> more specific about "something", need to take many steps?

 4.click browser to open it 
--> just open browser? I see same page as the test link you mentioned and no crash?

Before that's clarified I tend to say it's device-specific thus a candidate for de-nom in coming Triage.
Flags: needinfo?(wuchlin)
Flags: needinfo?(sync-1)
btw it's only seen in your test website when you repro. the issue? Or also seen in other normal website?

Comment 7

3 years ago
(In reply to Wesly Huang from comment #5)
> Hi TCL, ChengLin:
> 
> I can't repro. with Flame v188 (2.0) SW. would you clarify more about the
> STR?
> 
>  3.do someting ,such as going to setting,calling etc. 
> --> more specific about "something", need to take many steps?
> 
>  4.click browser to open it 
> --> just open browser? I see same page as the test link you mentioned and no
> crash?
> 
> Before that's clarified I tend to say it's device-specific thus a candidate
> for de-nom in coming Triage.

If you change the visibility of browser,  the browser will crash when opening a webpage contains wbmp picture. 

I think it is related with wbmp.
Flags: needinfo?(wuchlin)

Comment 8

3 years ago
There is a crash report on ffos1.3 at comment 2.  It's caused by mutex in wbmp decoder.
I'm not sure if wbmp is widely used now? Maybe low impact to user as rare use case? Still tend to be a de-nom candidate.

BTW is there a log for 2.0?
Flags: needinfo?(wuchlin)
Hi ChengLin, would you rovide log for 2.0?

As wbmp is not so widely used in nowadays so set this as de-tag candidate in coming 2.0 Triage.
Flags: needinfo?(wuchlin)
[Traige] de-tag.
blocking-b2g: 2.0? → -
Flags: needinfo?(sync-1)

Comment 12

3 years ago
Created attachment 8523666 [details]
Crash report on 2.0

Updated

2 years ago
Crash Signature: [@ PR_Lock | imgFrame::ImageUpdated(nsIntRect const&) ] → [@ PR_Lock | imgFrame::ImageUpdated(nsIntRect const&) ] [@ PR_Lock | imgFrame::ImageUpdated ]
link all Fire C (codename: Sora) bugs to a meta one.
Blocks: 1258646
You need to log in before you can comment on or make changes to this bug.