You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{
"ErrorMessage": "",
"ErrorPattern": "at Newtonsoft.Json.Linq.JArray.get_Item|GetValues: .*memory access out of bounds",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
Known issue validation
Build: 🔎 Result validation: ⚠️ Provided build not found. Provide a valid build in the "Build: 🔎" line. Validation performed at: 8/23/2023 4:28:55 AM UTC
Here the debugger test is calling into runtime via legacy JS interop method (probably on main thread) but it's not having correct GC transition barrier.
console.error: Error: [MONO] /__w/1/s/src/mono/mono/utils/mono-threads-state-machine.c:807 <disabled>
at It (http://localhost:9400/_framework/dotnet.runtime.js:3:13374)
Activity
pavelsavara commentedon Aug 4, 2023
RuntimeError: memory access out of boundsLogpavelsavara commentedon Aug 4, 2023
Here the debugger test is calling into runtime via legacy JS interop method (probably on main thread) but it's not having correct GC transition barrier.
@kg @lambdageek is my analysis right ?
In which case that should be separate issue.
Log
...snip
lambdageek commentedon Aug 4, 2023
Yea I think you're right @pavelsavara
thaystg commentedon Aug 15, 2023
I will work on it today.
pavelsavara commentedon Jan 21, 2024
So, legacy interop is gone now and with it the assumed GC boundary problems of it.
I see new issue
Log
Build
It look like deadlock.
jeffschwMSFT commentedon Feb 16, 2024
removing blocking-clean-ci as it has not failed in 30 days
lewing commentedon May 2, 2024
leaving open since these may still be running in servicing but these tests are disabled in main