Chrome crashes: STATUS_ACCESS_VIOLATION

[Florent Cadet]

Good evening,

I just tried to update to the latest beta 3 on my on premises staging. Some issues with the first upgrade since an addon (feature content) was completely crashing the site, I finally succeeded to upgrade doing a new fresh migration and disabling all the extra addons before to start.

The cache has been cleaned properly, I'm using a fresh new out of the box theme and I uninstalled all the custom addons I had before the upgrade.

My problem is now that the client area is just unstable for me and and chrome is crashing when I start to scroll a page, especially the home page which is instant crashing all the time. First, the page is correctly rendered, I start to scroll and Chrome displays the error attached to this post.

On the gallery, I can scroll and it happens rarely but it still happens sometimes.

Since is looks like a render issue, I have no issue at all on the front side (no error in dev tools console) and on the back side aswell.

Please note that I use a internal staging domain which is not reachable from the outside, I don't know if it can be a clue to this behaviour.

Any kind of idea to fix that will be appreciated.

UPDATE: I have no issue at all using Firefox, really strange and really complicated to debug

Edited November 2 by Florent Cadet

[Randy Calvert]

In Google searching the error, it appears to be a Chrome issue.

https://www.google.com/search?client=safari&rls=en&q=chrome+status_access_violation&ie=UTF-8&oe=UTF-8

 

[Florent Cadet]

On the chrome help page:

Quote

If other sites load fine, but only one site crashes, it's possible that site is causing the problem.

I have this issue only on this one and since I upgraded. I also cleared the browser cache.

[Marc]

This is generally a memory issue on the system using chrome

 

[Florent Cadet]

On 11/4/2024 at 11:42 AM, Marc said:

This is generally a memory issue on the system using chrome

 

I9 14900 32Gb ram 😇

[Marc]

16 hours ago, Florent Cadet said:

I9 14900 32Gb ram 😇

Im not entirely sure why you have given me those, to be honest 🙂 

[Florent Cadet]

18 hours ago, Marc said:

Im not entirely sure why you have given me those, to be honest 🙂 

You speak about chrome system memory... Chrome v.130.0.6723.92 / 130.0.6723.117, the issue is still there

If you want some technical ways to explore

 https://stackoverflow.com/questions/69161461/google-chrome-status-access-violation-error

https://stackoverflow.com/questions/76281364/status-access-violation-when-middle-clicking-page-ajax-php

[Marc]

Given what is being said there, please test this on a default unaltered theme. However the reality is, the bug is on chrome there

[G17 Media]

I had a similar issue on a beta/unstable Chromium build, the fix was, of course, using a stable Chrome version.

Edited November 7 by G17 Media

[Florent Cadet]

I found the root cause:

Enabling this feature in chrome://flags/ causes the page crash.

Considering

Quote

You can test features before they’re added to Chrome and give feedback.

I hope that a future chrome release will not brick it again.

[Randy Calvert]

Glad you found what was going on!  🙂 

[Marc]

Thank you for letting us know. Always handy when others come up with the same issue