Open Bug 1629470 Opened 4 years ago Updated 1 year ago

Crash in [@ DirectUI::DUIXmlParser::_EnterOnCurrentThread]

Categories

(External Software Affecting Firefox :: Other, defect, P5)

Unspecified
Windows 10

Tracking

(Not tracked)

People

(Reporter: gsvelto, Unassigned)

References

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-17919df3-e8b6-4601-b428-053cb0200411.

Top 10 frames of crashing thread:

0 dui70.dll DirectUI::DUIXmlParser::_EnterOnCurrentThread 
1 dui70.dll DirectUI::DUIXmlParser::CreateElement 
2 explorerframe.dll CSearchBoxDUIHost::_CreateFromResource 
3 explorerframe.dll CSearchBoxDUIHost::Create 
4 explorerframe.dll CSearchBox::Initialize 
5 explorerframe.dll CUniversalSearchBand::_Initialize 
6 explorerframe.dll CUniversalSearchBand::SetSite 
7 shcore.dll IUnknown_SetSite 
8 explorerframe.dll CBandSite::AddBand 
9 explorerframe.dll CNavBar::_CreateBands 

Not a new crash, this seems to be caused by a write to a NULL pointer in Microsoft DirectUI code. It seems to happen when we open a file dialog.

The priority flag is not set for this bug.
:gcp, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(gpascutto)

Very low amount of crashes, tricky to find the common source and thus identify the culprit.

Flags: needinfo?(gpascutto)
Priority: -- → P5
Assignee: nobody → tkikuchi
Severity: -- → S3
See Also: → 1771638

From looking at the reports, these may be OOM or close-to-OOM situations. Also exclusive to 32-bit builds.

Sorry, there was a problem with the detection of inactive users. I'm reverting the change.

Assignee: nobody → tokikuc

The bug assignee is inactive on Bugzilla, so the assignee is being reset.

Assignee: tokikuc → nobody
You need to log in before you can comment on or make changes to this bug.