[Webkit-unassigned] [Bug 260723] [GTK] Web process crash when creating GMainContext: Creating pipes for GWakeup: Too many open files

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Sep 3 07:04:22 PDT 2024


https://bugs.webkit.org/show_bug.cgi?id=260723

--- Comment #51 from Enrique Ocaña <eocanha at igalia.com> ---
So, the patch I brought in https://bugs.webkit.org/show_bug.cgi?id=264739 leaves "old" players in PAUSED state to avoid the last frame to disappear and become black on downstream platforms that need the player (and the internal platform-specific multimedia engine) working to show that last frame.

I see some options here:

a) Leave the decision to NOT move to READY and stay in PAUSED (old behaviour) as a Quirk  that would be enabled on specific downstream platforms.

b) Maintain a global queue of (weak?) references to MediaPlayerPrivate. For instance, holding the latest 20 active players in "PAUSED because of timeout" state. When more players need to be created and the maximum limit of "PAUSED because of timeout" active players (20) is reached, we start moving the oldest ones to READY, freeing resources at the expense of causing the "last frame shown as blank" issue that https://bugs.webkit.org/show_bug.cgi?id=264739 intended to fix.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20240903/ce201297/attachment.htm>


More information about the webkit-unassigned mailing list