Closed Bug 1324180 Opened 9 years ago Closed 8 years ago

Crash in DPA_ReleaseCB<T>

Categories

(Core :: Widget: Win32, defect, P3)

Product:
Core
Component:
Widget: Win32
Platform:
Unspecified
Windows 10
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox50 --- wontfix
firefox51 --- affected
firefox52 --- wontfix
firefox53 --- affected

People

(Reporter: jchen, Unassigned)

Details

(Keywords: crash, Whiteboard: [tpi:+][tbird crash][aes?])

Crash Data

This bug was filed from the Socorro interface and is report bp-f0dcbfff-461a-4cf7-acfc-942d42161216. ============================================================= Recent crashes started with the 12-12 Nightly, and since then, there has been at least one crash in every Nightly, although the volume is generally low. The crash happens in comdlg32.dll, and the top two libxul frames are, > RefPtr<>::~RefPtr<>() > nsFilePicker::ShowFilePicker(nsString const&, bool&) Looking at the 12-11 to 12-12 changes, I didn't see anything obvious.
Priority: -- → P3
Whiteboard: tpi:+
addon related? thunderbird crash also bp-d7e3e106-21b6-4836-a1db-9ab692161217
Whiteboard: tpi:+ → [tpi:+][tbird crash]
It's a Win10-only crash that appears to affect pretty much every version AFAICT. It's also 100% correlated to version 10.0.14986, which was promoted to the Slow Ring for users in the Insider program shortly before this bug was filed. Jim, can you help track this down based on that?
status-firefox50: --- → wontfix
status-firefox51: --- → affected
status-firefox52: --- → affected
status-firefox53: --- → affected
Flags: needinfo?(jmathies)
~99% of these (106/112) have accessibility enabled. The trigger seems to be freeing of com objects we have in RefPtrs when the file picker open method returns. Exact cause is unknown. Aaron, any ideas?
Flags: needinfo?(jmathies) → needinfo?(aklotz)
Whiteboard: [tpi:+][tbird crash] → [tpi:+][tbird crash][aes?]
No ideas. I'm not sure why a11y is correlated here.
Flags: needinfo?(aklotz)
Perhaps the a11y correlation is due to users with insider builds disproportionately running with touchscreens? Perhaps, perhaps not... Maybe we should report this to MSFT and go from there.
Mass wontfix for bugs affecting firefox 52.
status-firefox52: affected → wontfix
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.