Closed Bug 1137002 Opened 5 years ago Closed 5 years ago
Fix data races in Image
Lib related to off-main-thread On Data Available
We're seeing multiple TSan bugs (which are blocked by this bug) that suggest that we're accessing imgRequest fields from multiple threads in an unsynchronized way. The current bug reports involve mImage and mProgressTracker, but I want to be sure that everything we're doing is safe (especially since we have some crashes in this area of the code that are currently unexplained). As far as I'm aware, imgRequest::OnDataAvailable is the only method we're calling off-main-thread. (Well, that and the methods that it calls transitively.) So this bug boils down to making sure that all the state that OnDataAvailable touches is threadsafe. I think there are really a few different sub-issues here, so let's treat this as a metabug.
This should be ready to resolve, but I'd like to wait for verification that ASAN doesn't report any more warnings in this code.
OK, I think we're finally ready to resolve this. Nathan, please reopen (or file a new bug) if you hit any further TSan issues in this area of the code.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.