Don't call CreateSurfaceForWindow in MakeCurrent in EGL

RESOLVED FIXED in mozilla13

Status

()

RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: BenWa, Assigned: BenWa)

Tracking

unspecified
mozilla13
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

7 years ago
Created attachment 597456 [details] [diff] [review]
patch

I don't think it make sense to call CreateSurface in EGL. We're not ready to provide a surface in all cases, in particular shutdown in Maple.

I suggest that we bind a context with a surface. This lets shutdown continue without deadlocking/crashing.

I plan on also landing this fix on m-c to reduce the merge diff.
Attachment #597456 - Flags: review?
(Assignee)

Updated

7 years ago
Attachment #597456 - Flags: review? → review?(ajuma)

Comment 1

7 years ago
Comment on attachment 597456 [details] [diff] [review]
patch

Review of attachment 597456 [details] [diff] [review]:
-----------------------------------------------------------------

I'd add a comment that we're doing this to allow cleanup to proceed (as opposed to just bailing and returning false when we don't have a surface).
Attachment #597456 - Flags: review?(ajuma) → review+
(Assignee)

Comment 2

7 years ago
Created attachment 597514 [details] [diff] [review]
patch + comment
Assignee: nobody → bgirard
Attachment #597456 - Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #597514 - Flags: review?(ajuma)

Comment 3

7 years ago
Comment on attachment 597514 [details] [diff] [review]
patch + comment

Review of attachment 597514 [details] [diff] [review]:
-----------------------------------------------------------------

"bind the surface" -> "bind NO_SURFACE"
"wont" -> "won't"
Attachment #597514 - Flags: review?(ajuma) → review+

Comment 6

7 years ago
https://hg.mozilla.org/mozilla-central/rev/4988f2f80c44
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla13
You need to log in before you can comment on or make changes to this bug.