Closed Bug 1866657 Opened 2 years ago Closed 2 years ago

Crash in [@ std::fill]

Categories

(Core :: JavaScript Engine, defect, P3)

Other
Windows 11
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox122 --- affected

People

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

References

(Blocks 2 open bugs)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/f71538be-2dd6-4311-8069-9cd1e0231124

Reason: EXCEPTION_ACCESS_VIOLATION_WRITE

Top 10 frames of crashing thread:

0  xul.dll  std::fill  /builds/worker/fetches/vs/VC/Tools/MSVC/14.29.30133/include/xutility:4484
0  xul.dll  std::_Hash_vec<v8::internal::ZoneAllocator<std::_List_unchecked_iterator<std::_List_val<std::_List_simple_types<std::pair<const int, v8::internal::  /builds/worker/fetches/vs/VC/Tools/MSVC/14.29.30133/include/xhash:297
1  xul.dll  std::_Hash<std::_Umap_traits<int, v8::internal::  /builds/worker/fetches/vs/VC/Tools/MSVC/14.29.30133/include/xhash:365
1  xul.dll  std::unordered_map<int, v8::internal::  /builds/worker/fetches/vs/VC/Tools/MSVC/14.29.30133/include/unordered_map:137
1  xul.dll  v8::internal::ZoneUnorderedMap<int, v8::internal::  js/src/irregexp/util/ZoneShim.h:397
1  xul.dll  v8::internal::  js/src/irregexp/imported/regexp-bytecode-peephole.cc:280
2  xul.dll  v8::internal::Zone::New  js/src/irregexp/util/ZoneShim.h:34
2  xul.dll  v8::internal::  js/src/irregexp/imported/regexp-bytecode-peephole.cc:477
2  xul.dll  v8::internal::RegExpBytecodePeepholeOptimization::OptimizeBytecode  js/src/irregexp/imported/regexp-bytecode-peephole.cc:1012
3  xul.dll  v8::internal::RegExpBytecodeGenerator::GetCode  js/src/irregexp/imported/regexp-bytecode-generator.cc:382

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

  • First crash report: 2023-11-11
  • Process type: Content
  • Is startup crash: No
  • Has user comments: No
  • Is null crash: Yes - 1 out of 3 crashes happened on null or near null memory address
  • Is use after free crash: Yes - 1 out of 3 crashes happened on or near an allocator poison value

All crashes seem to come from the same user, even though it is 3 different installations.

Group: core-security → javascript-core-security
Component: General → JavaScript Engine

I only see 17 crashes in the last 6 months, and only one of them is on a poison value. Given that they are coming from the same machine, let's just unhide this.

Group: javascript-core-security
Severity: -- → S3
Priority: -- → P3

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.