Closed Bug 916058 Opened 6 years ago Closed 2 years ago

Next paint seems too late to happen after 905116

Categories

(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: alive, Assigned: alive)

References

Details

STR:
1. Open browser app
2. Press home
3. Open browser again

AppWindow Log:
[appWindow][app://browser.gaiamobile.org][1379065308.161]publish: resize
[appWindow][app://browser.gaiamobile.org][1379065308.17]set visibility -> ,true
[appWindow][app://browser.gaiamobile.org][1379065308.174]screenshot state -> ,frame
[appWindow][app://browser.gaiamobile.org][1379065308.23]publish: foreground
[appWindow][app://browser.gaiamobile.org][1379065309.17] nextpaint is timeouted.
[appWindow][app://homescreen.gaiamobile.org][1379065309.185]transition state changed from opened, to ,closing, by ,close
[appWindow][app://homescreen.gaiamobile.org][1379065309.22]publish: closing
[appWindow][app://homescreen.gaiamobile.org][1379065309.509]set visibility -> ,false
[appWindow][app://homescreen.gaiamobile.org][1379065309.541]screenshot state -> ,none
[appWindow][app://homescreen.gaiamobile.org][1379065309.643]transition state changed from closing, to ,closed, by ,timeout
[appWindow][app://homescreen.gaiamobile.org][1379065309.647]set visibility -> ,false
[appWindow][app://homescreen.gaiamobile.org][1379065309.657]screenshot state -> ,none
[appWindow][app://homescreen.gaiamobile.org][1379065309.662]publish: closed
[appWindow][app://homescreen.gaiamobile.org][1379065309.67]publish: background

There is nearly 1S between visibilitychange and nextpaint. This is really strange.
I decides to callback right away when nextpaint callback is registered. But we need to find out why this happens.
Component: Gaia::System → Gaia::System::Window Mgmt
No longer blocks: task-manager
Make meta bug clear
No longer blocks: window-management
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.