Closed Bug 1901342 Opened 1 month ago Closed 13 days ago

Startup crash in [@ nsTSubstring<T>::AllocFailed | nsTSubstring<T>::Assign | nsTSubstring<T>::Assign | nsLocalFile::EnsureShortPath]

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Platform:
Other
Windows 11
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE
Tracking Flags:
Tracking Status
firefox129 --- affected

People

(Reporter: release-mgmt-account-bot, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/30245227-41a5-4ca8-bdf3-b86cc0240602

Reason: EXCEPTION_ILLEGAL_INSTRUCTION

Top 10 frames of crashing thread:

0  xul.dll  nsTSubstring<char16_t>::AllocFailed  xpcom/string/nsTSubstring.h:1217
0  xul.dll  nsTSubstring<char16_t>::Assign  xpcom/string/nsTSubstring.cpp:402
0  xul.dll  nsTSubstring<char16_t>::Assign  xpcom/string/nsTSubstring.h:437
0  xul.dll  nsLocalFile::EnsureShortPath  xpcom/io/nsLocalFileWin.cpp:3642
0  xul.dll  nsLocalFile::Equals  xpcom/io/nsLocalFileWin.cpp:3138
1  xul.dll  CheckCompatibility  toolkit/xre/nsAppRunner.cpp:3453
2  xul.dll  XREMain::XRE_mainStartup  toolkit/xre/nsAppRunner.cpp:5162
3  xul.dll  XREMain::XRE_main  toolkit/xre/nsAppRunner.cpp:5973
4  xul.dll  XRE_main  toolkit/xre/nsAppRunner.cpp:6042
5  firefox.exe  do_main  browser/app/nsBrowserApp.cpp:230

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

  • First crash report: 2024-06-02
  • Process type: Parent
  • Is startup crash: Yes - all crashes happened during startup
  • Has user comments: No
  • Is null crash: No
Component: General → XPCOM

This is actually an OOM crash. I don't know why it is showing up like this.

See Also: → 1901269

The severity field is not set for this bug.
:nika, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(nika)

Apparently the crash reports have a decoded instruction which doesn't match the instruction which is supposed to be at that address, which implies some amount of memory corruption or similar. There are also relatively few unique install times. I don't think there's anything we can do for this low-volume startup crash occurring in what appears to be a corrupted string OOM codepath.

Status: NEW → RESOLVED
Closed: 13 days ago
Flags: needinfo?(nika)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.