Closed Bug 717938 Opened 13 years ago Closed 6 months ago

OMTC: ChildView's access to compositor's GL context should be thread-safe

Categories

(Core :: Graphics, defect)

Product:
Core
Component:
Graphics
Platform:
x86
macOS
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE
Tracking Flags:
Tracking Status
e10s later ---

People

(Reporter: ajuma, Unassigned)

References

Details

With OMTC and GL layers on OS X, LayerManagerOGL (on the compositor thread) owns the GL context, but ChildView (on the main thread) also needs access to this GL context (e.g. so it can call [mGLContext update] to notify the GL context of a size change). We need to ensure that the main thread and the compositor thread never simultaneously access the GL context.
No longer blocks: omtc
Blocks: omtc
Mass tracking-e10s flag change. Filter bugmail on "2be0fcce-e36a-4e2c-aa80-0e3d33eb5406".
tracking-e10s: --- → +
Severity: normal → S3

OMTC is long gone.

Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.