Closed Bug 1171978 Opened 9 years ago Closed 9 years ago

avoid video stream leakage (probably masked by window teardown, at least)

Categories

(Hello (Loop) :: Client, defect)

Product:
Hello (Loop)
Component:
Client
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: dmosedale, Unassigned)

References

Details

User Story

As a user, my browser shouldn't using unnecessary memory while in a Hello conversation.

We probably want to do most (maybe all) of these things at some point, whether or not as part of this bug:

* create LocalVideoDisabled action (but taking into account any changes from bug 1171969
* TDD dispatch from various places in otSdkDriver
* TDD use by stores and views
* either add mediaView.detachVideo, or switch attachVideo into syncVideo which would do both I don't think this is a real problem at the moment - if remote video goes away, then we're tearing down the video DOM element. Likewise with local video & screen share.
      No description provided.
Depends on: 1141296
After reviewing the work in bug 1203529, and the way our media views work, I think this is now WFM:

- The media views don't display the video element when streams aren't active, so the video would be released/detached.
- The work in bug 1203529 makes it so that the stores definitely no longer retain a copy of the stream element after the time a stream is notified as being destroyed by the sdk.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.