Closed Bug 1010254 Opened 11 years ago Closed 11 years ago

FFOS should not needlessly lose GL contexts.

Categories

(Core :: Graphics: CanvasWebGL, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 999878

People

(Reporter: jujjyl, Unassigned)

Details

Attachments

(1 file)

Attached file Archive.zip
Playing around with a test application (attached), I notice that whenever pushing the home button to enter the home screen from a packaged app, there seems to be some kind of timer that automatically causes the GL context in the packaged app to be lost when it is put into background. That is, - if I quickly resume the application, the GL context has not been lost and the application is able to resume without having to recreate its GPU resources. - if I instead wait for a second or two, a some kind of GL context loss timer kicks in and sends the packaged app in the background a webglcontextlost message, even though no other application that requires the GPU is activated in between. Is this observation correct? Why does the GL context become spontaneously lost when in the main screen? There does not seem to be a reason for that (i.e. some other application consuming the GPU) Could the webglcontextlost message be sent to the background application only when it actually does lose the context due to another application actually consuming GPU resources? That would allow better responsiveness when users could switch between an app and the homescreen, and perhaps even between multiple apps, if not all the apps required heavy GPU resource consumption.
Oh, I realize this is a duplicate of existing entry.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: