Description
Description
Faulting application name: internalWeb.exe, version: 2.6.2935.0, time stamp: 0x67200000
Faulting module name: coreclr.dll, version: 9.0.24.52809, time stamp: 0x672049fc
Exception code: 0xc0000005
Fault offset: 0x00000000002eea8b
Faulting process id: 0x649c
Faulting application start time: 0x01db3988d312000b
Faulting application path: C:\Program Files\3DBackup\bin\internalWeb.exe
Faulting module path: C:\Program Files\3DBackup\bin\coreclr.dll
Report Id: 8d1a48a5-e27f-4a5f-acbf-1d40624ed842
Reproduction Steps
This happened 2 nights running before I backed out the migration to .net 9.
I have not isolated the fault.
WER reported the issue and captured data on both occasions:
Report Id: 8d1a48a5-e27f-4a5f-acbf-1d40624ed842
Report Status: 268435456
Hashed bucket: 2e7dfb54d62033d3fc1a7aa712618a8b
Report Id: 324f8194-84f9-4ced-b429-27044b78e4d5
Report Status: 268435456
Hashed bucket: 3700e920166dc8b4904ac6c8801323ea
Expected behavior
Not crashing.
Actual behavior
STATUS_ACCESS_VIOLATION in coreclr.dll crashes the app.
Regression?
Yes. The same code runs fine in .net 8, has been in production, and on customer sites.
Known Workarounds
None.
Configuration
.net sdk 9.0.100
aspnet core.
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.19045 N/A Build 19045
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Workstation
OS Build Type: Multiprocessor Free
Product ID: 00330-51446-83390-AAOEM
Original Install Date: 27/05/2022, 1:27:58 pm
System Boot Time: 13/11/2024, 9:28:29 pm
System Manufacturer: HP
System Model: HP Z240 Tower Workstation
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 94 Stepping 3 GenuineIntel ~4001 Mhz
BIOS Version: HP N51 Ver. 01.70, 19/06/2018
Total Physical Memory: 32,553 MB
Other information
No response