Remove the locking assertions in BufferTextureClient until ContentClient locking is fixed

RESOLVED FIXED in mozilla29

Status

()

Core
Graphics: Layers
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: nical, Assigned: nical)

Tracking

unspecified
mozilla29
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

4 years ago
I added locking assertions in BufferTextureClient as part of the D3D texture work, a bit too early because these assertions are consistently hit as long as 952507 is not fixed. we should remove them temporarily and add them back when ContentClient is fixed. At the moment this completely breaks OMTC on Linux.
(Assignee)

Comment 1

4 years ago
Created attachment 8357748 [details] [diff] [review]
Turn the failing assertions into warnings for now
Attachment #8357748 - Flags: review?(bjacob)
Attachment #8357748 - Flags: review?(bjacob) → review+
(Assignee)

Comment 2

4 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/b7b3afa4c103
https://hg.mozilla.org/mozilla-central/rev/b7b3afa4c103
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
You need to log in before you can comment on or make changes to this bug.