SharedBufferManagerChild probably leaks mTransport

NEW
Unassigned

Status

()

Core
Graphics: Layers
2 years ago
2 years ago

People

(Reporter: mccr8, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox44 affected)

Details

(Whiteboard: [gfx-noted])

(Reporter)

Description

2 years ago
The dtor for SharedBufferManagerChild needs the same boilerplate as ~SharedBufferManagerParent to delete mTransport. Assuming this code is B2G-only, this leak wouldn't show up in any testing we do. Of course, if this actor lives as long as the process anyways, then this leak should not be an actual concern until we start doing leak checking in content processes.
You need to log in before you can comment on or make changes to this bug.