This bug was filed from the Socorro interface and is report bp-071ce38a-9f59-479c-a04c-b9fa82170218. ============================================================= We've had crashes in the past with this signature, but this is clearly a new crash that started in Nightly 20170217030229, where it is the Windows #9 topcrash. My guess is that bug 1337559 is at fault, although that did land on 2017-02-14, which is slightly earlier than I would have expected. jya, can you please investigate?
The crash address appears to always be 0x38 on x86 and 0x50 on x86-64. Probably a null pointer deref, perhaps due to a null mDrainPromise?
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1341210
You need to log in before you can comment on or make changes to this bug.