Closed Bug 921002 Opened 11 years ago Closed 6 years ago

[B2G][Helix][browser][wufumin]The webpage will white screen or turn to blank when resize the webpage

Categories

(Firefox OS Graveyard :: General, defect, P1)

defect

Tracking

(blocking-b2g:-)

RESOLVED WONTFIX
blocking-b2g -

People

(Reporter: lecky.wanglei, Unassigned)

References

Details

Attachments

(7 files)

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; aff-kingsoft-ciba)

Steps to reproduce:

1.open browser,enter a website address and go
2.after the webpage loaded,resize the webpage using fingers




Actual results:

The webpage will white screen or turn to blank when resize the webpage


Expected results:

The webpage will no white screen or turn to blank when resize the webpage
Severity: normal → blocker
Priority: -- → P1
hi,if I remove the file of hwcomposer.msm7627a.so.This problem can still be reproduced. so I think the problem is mozllia problem.
Software versions and details please.
Flags: needinfo?(lecky.wanglei)
Also, is this during resizing or does the page stay blank AFTER resizing has completed?
No,I do thinks so.If  we test another phone,we can't see blank.but only the phone of mozilla,we can see log time of blank. I think the problem  affect the basic functions.

thanks
wufumin
Flags: needinfo?(lecky.wanglei)
blocking-b2g: --- → hd?
Flags: needinfo?(wchang)
 My build info as following:
gaia:c0ea0a4943dc8d3751b07f5b5c5d3abe06364a14  
gecko:170f9e477571127cd40997fa2abe262ed43f0e4d
v1.1 release
Flags: needinfo?(wchang)
hi, Wayne Chang 
please analsye the issue.
thanks wufumin
Flags: needinfo?(wchang)
Flags: needinfo?(johu)
Flags: needinfo?(dwilson)
hi beatriz:
Could you help us to push this issue to be solved?
We think this issue is a original Mozilla bug because of the WVGA mechanism of V1.1HD.
Flags: needinfo?(brg)
Attached file video.part1.rar
Attached file video.part2.rar
Attached file video.part4.rar
Attached file video.part5.rar
Attached file video.part3.rar
Checked attached video from comment 10 to 14, the blinking is transitional and for a short interval only.

Not blocking on this.
blocking-b2g: hd? → ---
Flags: needinfo?(wchang)
hi, Wayne Chang 
can you find this issue on v1.1?
sometimes,we find the webpage will long time white screen or turn to blank .you can check it on on v1.1.
blocking-b2g: --- → hd?
(In reply to lecky from comment #17)
> sometimes,we find the webpage will long time white screen or turn to blank
> .you can check it on on v1.1.

Do you mean the phenomenon described in bug 908632? In which case you'd have to check on your side.

For what's seen in the video in this bug, we will not block on these recoverable transitional performance bugs.
blocking-b2g: hd? → ---
 hi, Wayne Chang 
can you find this issue on v1.1?
if I remove the file of hwcomposer.msm7627a.so.This problem can still be reproduced
(In reply to lecky from comment #19)
>  hi, Wayne Chang 
> can you find this issue on v1.1?
> if I remove the file of hwcomposer.msm7627a.so.This problem can still be
> reproduced

OK, looks like this is reproducible on GPU composition as well. If that's the case then the prob is not on my neck of the woods (hwc).
Flags: needinfo?(dwilson)
hi, Wayne Chang  、 Diego Wilson and 
I test the issue on the code of mozilla native  which we don't modify .At the same  time I remove the file of hwcomposer.msm7627a.so , I still can find this issue.
From this issue ,we think it is mozilla problem.

This problem affects the basic functions.If you have  no plan to solve the problem in v1.1 and 1.1HD  release .please tell me?

hi beatriz:
Could you help us to push this issue to be solved?
We think this issue is a original Mozilla bug because of the WVGA mechanism of V1.1HD.
Vincent Lin will look into this. We found this phenomenon is more visible on HD devices including on the nexus.
Flags: needinfo?(vlin)
Can someone provide a website which can reproduce this issue easily ?

I just tried a few websites on N4 device, but not reproducible.

This issue seems website-dependent.
Flags: needinfo?(vlin)
Depends on: 925656
(In reply to lecky from comment #21)
> hi beatriz:
> Could you help us to push this issue to be solved?
> We think this issue is a original Mozilla bug because of the WVGA mechanism
> of V1.1HD.
Lecky, please answer comment 23
Flags: needinfo?(brg) → needinfo?(lecky.wanglei)
My bad~
It's not website-dependent. The critical point is zooming.
hi,I am sorry answer later

you can visit the web http://news.163.com/  www.ifeng.com

 
(In reply to Vincent Lin[:vincentlin] from comment #23)
> Can someone provide a website which can reproduce this issue easily ?

I
> just tried a few websites on N4 device, but not reproducible.

This issue
> seems website-dependent.
Flags: needinfo?(lecky.wanglei)
yes ,if we zoom in or out the webpage, the  issue will become  bad. 

(In reply to Vincent Lin[:vincentlin] from comment #25)
> My bad~
It's not website-dependent. The critical point is zooming.
Flags: needinfo?(johu)
hi,
Flags: needinfo?(vlin)
Flags: needinfo?(vlin) → needinfo?(brg)
I am sorry to disturb you.what ahout the issue.the problem just like to zoom in or out the pciture,when we enter the gallery.
blocking-b2g: --- → hd?
(In reply to Beatriz Rodríguez [:brg] from comment #24)
> (In reply to lecky from comment #21)
> hi beatriz:
> Could you help us to
> push this issue to be solved?
> We think this issue is a original Mozilla
> bug because of the WVGA mechanism
> of V1.1HD.
> Lecky, please answer comment
> 23

Hi beatriz:
you can visit the web http://news.163.com/  www.ifeng.com  (10% percentage)
Wayne has said this issue would not not block V1.1HD ,could you accept the conclusion? What's your opionion?


Hi Wayne && Vincent Lin
As you comment 25 , you have reproduced this issue, we think you need to evaluate again whether need to solve it on V1.1 HD . We think it is important.

And if you can give us some help && guideline to solve this issue by ourselves such as that tell us some clues of the code project, we will be very glad to solve it by ourselves.

Thank you very much!
Hope for your reply!
Flags: needinfo?(wchang)
Flags: needinfo?(vlin)
Hi beatriz:
I test again ,If we  zoom picutre ,the issue can reproduce 100%.
Not a blocker for v1.1. But a nice to improve in v1.2. Nominating accordingly.
blocking-b2g: hd? → koi?
Flags: needinfo?(brg)
Vincent is working on this but we have no plans to back port the fix to v1.1 given its non-blocker status and the amount of work/effort involved with the fix.
Flags: needinfo?(wchang)
Hi beatriz:
I test again ,If we  zoom webpage ,the issue can reproduce 100%.could you accept the issue too?
Flags: sec-review?
Flags: needinfo?(vlin)
Flags: needinfo?(brg)
Please do not set the security review flag, this is not what it is for. 
It's for bugs with security concern.
Flags: sec-review?
hi,Vincent

can you give some advice how to solve the issue. If you can ,can give me about  the root cause .and where modify?

thanks


If we want solve the issue ,can you give me some advice .and can you tell me how many 
(In reply to Vincent Lin[:vincentlin] from comment #25)
> My bad~
It's not website-dependent. The critical point is zooming.
Flags: needinfo?(vlin)
Hi,

Beatriz has already confirmed that this is not blocking v1.1 and nominated it for 1.2.

Removing ni.

Br
Flags: needinfo?(brg)
Bug 925656 is looking into this kind of problem. It looks graphic performance issue.
Flags: needinfo?(vlin)
nice to have in 1.2. minus for 1.2
blocking-b2g: koi? → -
hi,we print the parameter  of layer .why the sourceCrop.top and   2633 is so big.  


11-06 20:57:54.890: E/HWComposer(185): TryRender : mList->numHwLayers[3]
11-06 20:57:54.890: E/HWComposer(185):  compositionType = 2;
11-06 20:57:54.890: E/HWComposer(185):  hints = 0;
11-06 20:57:54.890: E/HWComposer(185):  flags = 0;
11-06 20:57:54.890: E/HWComposer(185):  transform = 0;
11-06 20:57:54.890: E/HWComposer(185):  blending = 261;
11-06 20:57:54.890: E/HWComposer(185):  sourceCrop.left = 0;
11-06 20:57:54.890: E/HWComposer(185):  sourceCrop.top = 1581;
11-06 20:57:54.890: E/HWComposer(185):  sourceCrop.right = 720;
11-06 20:57:54.890: E/HWComposer(185):  sourceCrop.bottom = 2633;
11-06 20:57:54.890: E/HWComposer(185):  displayFrame.left = 0;
11-06 20:57:54.890: E/HWComposer(185):  displayFrame.top = 30;
11-06 20:57:54.890: E/HWComposer(185):  displayFrame.right = 480;
11-06 20:57:54.890: E/HWComposer(185):  displayFrame.bottom = 731;


11-06 20:57:54.910: E/copybit(185): 0: src={w=736, h=2656, f=1, rect={0,1581,720,1052}}
11-06 20:57:54.910: E/copybit(185):     dst={w=480, h=800, f=14, rect={0,30,480,701}
Attached file ddms.txt
Flags: needinfo?(vlin)
I don't know why the the parameter  of layer  is so big.I am not sure whether the hal can handle the big parameter .
It just means the source image is large and source cropping happens at the moment.
Flags: needinfo?(vlin)
yes, we can cee the big layer at the moment of the  webpage will white screen .
can you explain?
I am very worried the big layer which  cause white.
Flags: needinfo?(vlin)
It has to be a large layer for webpage.

We won't fix it in 1.2.
Flags: needinfo?(vlin)
can you tell me the root cause?o
(In reply to Vincent Lin[:vincentlin] from comment #46)
> It has to be a large layer for webpage.

We won't fix it in 1.2.
Flags: needinfo?(vlin)
(In reply to lecky from comment #47)
> can you tell me the root cause?o

We're improving graphics/layout performance which might be helpful for this.
Flags: needinfo?(vlin)
hi,Vincent Lin
can you tell me how to modify?
we can try the modify in 1.1HD?
Flags: needinfo?(vlin)
hi,can you tell me which bug talk about this issue?
The meta bug 920921 would help on this.
Flags: needinfo?(vlin)
Firefox OS is not being worked on
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: