Open Bug 1884469 Opened 2 months ago Updated 2 months ago

Crash in [@ __delayLoadHelper2 | <unknown in firefox.pdb>]

Categories

(Core :: Security: Process Sandboxing, defect, P2)

Other
Windows
defect

Tracking

()

Tracking Status
firefox125 --- affected

People

(Reporter: release-mgmt-account-bot, Assigned: bobowen)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/5c0a8ebb-9e61-423a-8000-c04510240308

Reason: FACILITY_VISUALCPP / ERROR_MOD_NOT_FOUND

Top 10 frames of crashing thread:

0  KERNELBASE.dll  RaiseException  
1  firefox.exe  __delayLoadHelper2  /builds/worker/workspace/obj-build/browser/app/D:/a/_work/1/s/src/vctools/delayimp/delayhlp.cpp:301
2  firefox.exe  <unknown in firefox.pdb>  
3  firefox.exe  sandbox::CreateAltWindowStation  security/sandbox/chromium/sandbox/win/src/window.cc:42
4  firefox.exe  sandbox::PolicyBase::CreateAlternateDesktop  security/sandbox/chromium/sandbox/win/src/sandbox_policy_base.cc:221
5  firefox.exe  mozilla::sandboxing::InitializeBrokerServices  security/sandbox/win/SandboxInitialization.cpp:178
6  firefox.exe  mozilla::sandboxing::GetInitializedBrokerServices  security/sandbox/win/SandboxInitialization.cpp:187
7  firefox.exe  do_main  browser/app/nsBrowserApp.cpp:211
7  firefox.exe  NS_internal_main  browser/app/nsBrowserApp.cpp:445
7  firefox.exe  wmain  toolkit/xre/nsWindowsWMain.cpp:174

By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:

  • First crash report: 2023-12-30
  • Process type: Parent
  • Is startup crash: No
  • Has user comments: No
  • Is null crash: Yes - 6 out of 15 crashes happened on null or near null memory address

The Bugbug bot thinks this bug should belong to the 'Core::Security: Process Sandboxing' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: General → Security: Process Sandboxing
Assignee: nobody → bobowencode
Severity: -- → S3
Priority: -- → P2

These all actually appear to be a failure to delay load user32.dll in the parent process.

So to clarify: sandboxing gets "blamed" here because it's one of the first things in the startup path.

You need to log in before you can comment on or make changes to this bug.