Closed
Bug 841940
Opened 11 years ago
Closed 11 years ago
getUserMedia leaks in crashtests if the permission UI is enabled
Categories
(Core :: WebRTC, defect)
Core
WebRTC
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: jesup, Unassigned)
References
Details
(Whiteboard: [getUserMedia][blocking-gum-])
Attachments
(1 file, 1 obsolete file)
71.32 KB,
text/plain
|
Details |
If the permission UI is enabled in crashtests, a single call to getUserMedia({}, {}, {}) will leak a ton of objects, though none appear to be webrtc-related. Perhaps a document is leaking. I'll note that crashtests don't have regular chrome, unlike mochitests. If you replace dom/media/crashtests with this: default-preferences pref(media.peerconnection.enabled,true) load 802892.html it leaks the world. You can remove the for loop in 802892.html, and only call mozGetUserMedia() once and it still leaks. If you add pref(media.navigator.permission.disabled,true) to the default-preferences line, it won't leak (and it doesn't try to contact the UI).
Reporter | ||
Comment 1•11 years ago
|
||
Attachment #714637 -
Attachment is obsolete: true
Reporter | ||
Comment 2•11 years ago
|
||
Note: I'm not sure that invoking the permission UI is reasonable in a crashtest.
Whiteboard: [getUserMedia][blocking-gum?]
Comment 3•11 years ago
|
||
(In reply to Randell Jesup [:jesup] from comment #2) > Note: I'm not sure that invoking the permission UI is reasonable in a > crashtest. Probably isn't. Dao - Any ideas why we leak the world in this bug?
Flags: needinfo?(dao)
Comment 4•11 years ago
|
||
I actually don't think this one blocks - we are only seeing this happening with fake streams at the moment and may be a crash only issue. If it turns out this ends up being something bigger, then let's reconsider the blocking flag.
Whiteboard: [getUserMedia][blocking-gum?] → [getUserMedia][blocking-gum-]
Comment 5•11 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #4) > I actually don't think this one blocks - we are only seeing this happening > with fake streams at the moment and may be a crash only issue. If it turns > out this ends up being something bigger, then let's reconsider the blocking > flag. Actually, my wording is wrong here. Let me try again. I don't think this blocks at the moment because I think this potentially could be an issue that we can't call gUM without fake in CI. If we see this outside of CI or confirm it's possible to be outside of CI, then let's reconsider.
Reporter | ||
Comment 6•11 years ago
|
||
dolske said on IRC he didn't believe invoking the permissions UI in a crashtest was a relevant test, and might cause some unexpected issues in that framework. It would be nice to understand why this happens, but not mandatory. We may want to consider closing this bug.
Comment 7•11 years ago
|
||
(In reply to Randell Jesup [:jesup] from comment #6) > dolske said on IRC he didn't believe invoking the permissions UI in a > crashtest was a relevant test, and might cause some unexpected issues in > that framework. > > It would be nice to understand why this happens, but not mandatory. We may > want to consider closing this bug. Sounds fine to me.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(dao)
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•