Chrome Aw Snap! STATUS_BREAKPOINT for pyodide, with Antivirus such as Cylance or Sophos #462
Replies: 2 comments 1 reply
-
|
Library author here, thanks for your report! This seems like a severe problem, so I would like more info : I cannot reproduce your issue at the moment (tried on Chrome + Edge on Windows 11 ARM). I would need more details: Did you try with another windows PC? Please do try with another PC. This will give us more insight about the issue. Do you have issues with the bare pyodide REPL demo? https://pyodide.org/en/stable/console.html This will load only pyodide. If you have issues in here, then pyodide is the likely culprit. When it fails, are you able to see anything in the logs before the dev tools fail? Below is a common startup sequence in the logs, up to where does it go? Can you try the minimal app source code and use it to make more diagnostic
|
Beta Was this translation helpful? Give feedback.
-
|
I just did an intensive test on another Windows PC (x64) and I could not reproduce the issue on Chrome and Edge although I restarted Chrome several times and reloaded the page about 30 times. This looks similar to this issue on the pyodide repo: Chrome crashed with "Aw, Snap!" on Windows due to 'StackPivot' exploit prevention by Sophos Endpoint Agent Is there a browser hardening policy on your computer that might cause this (or an antivirus such as Sophos)? Anyhow, I would like more info on your side. Leaving this discussion open so that other users may post their status. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Been finding this mainly on windows machines with chrome or edge, after pyodide apps load all the wheels and start the main entrypoint, they can just crash to the (Sad folder face) "Aw, Snap! Something went wrong while displaying this webpage. Error code: STATUS_BREAKPOINT".
With custom pyodide apps built with 1.92.700 and earlier versions. Even simply the https://traineq.org/probabl/ demo page.
It's a strange non-reproducible thing, multiple reloads sometimes works. Sometimes it will load and then crash after 1 sec. Other times, once it is fully loaded it is pretty stable.
Hard to get much from chrome logging,
--v=1 --enable-logging=stderrwill just end with nothing logged when STATUS_BREAKPOINT shows up, and the browser just completely nukes the dev tools, console, etc so can't see any debugging info there.Have you run into this or heard of this for pyodide apps? Not having any issues on linux with chrome, just windows.
Very little from google searching but one example in the wild: pyodide/pyodide#4774
Beta Was this translation helpful? Give feedback.
All reactions