Bug 115693

Summary: Media element leaking in Youtube for iPad
Product: WebKit Reporter: Philippe Normand <pnormand>
Component: MediaAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: allan.jensen, ap, ehdgms, eric.carlson, james.hilliard1, jer.noble
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   

Philippe Normand
Reported 2013-05-06 19:27:04 PDT
Loading youtube.com with the user-agent of the iPad, play one video, wait a few seconds and click on another video on the right side list. The first media element and its associated MediaPlayer/MediaPlayerPrivate is not destroyed. I can reproduce this issue with the GTK MiniBrowser at least. In the GNOME Sound properties I can see the WebProcess keeps the sound card open for 2 connections.
Attachments
Eric Carlson
Comment 1 2013-05-06 21:50:29 PDT
(In reply to comment #0) > Loading youtube.com with the user-agent of the iPad, play one video, wait a few seconds and click on another video on the right side list. The first media element and its associated MediaPlayer/MediaPlayerPrivate is not destroyed. > This implies that it is a bug in the youtube.com code used when they think user is on an iPad.
Dongheun Kang
Comment 2 2013-05-13 19:56:40 PDT
There is a web page created by this way. For example, videojs.com. recreate video element.
Allan Sandfeld Jensen
Comment 3 2013-08-05 06:07:22 PDT
If you implement the activity triggered garbage collector (GCActivityCallback), the garbage collection will trigger sooner or later when new JS objects are allocated.
James Hilliard
Comment 4 2022-07-17 20:30:29 PDT
(In reply to Philippe Normand from comment #0) > The first media element and its associated MediaPlayer/MediaPlayerPrivate is not destroyed. This looks somewhat similar to the issue I'm seeing in https://bugs.webkit.org/show_bug.cgi?id=241549 > In the GNOME Sound properties I can see the WebProcess keeps the sound card open for 2 connections. I'm seeing this except with WPEWebProcess connections in pipewire.
Note You need to log in before you can comment on or make changes to this bug.