Hi @bws-online
I looked a bit around, because I’ve never seen this error before.
Looks like it’s a Chromium-based browser error (https://wordpress.com/forums/topic/result_code_hung-crashing-while-working-at-the-backend/)
Have you tried another browser?
/A
-
This reply was modified 1 year, 3 months ago by
kuckovic.
Thread Starter
bdd
(@bws-online)
Thanks for the reply @kuckovic.
I’ve tried Firefox, Brave, Chrome, and Edge, regular and private/incognito tabs.
Looking at the loading icon in the synced pattern (for the first instance on the page since I can’t scroll further) and the admin dashboard screen (editing the content or trying to choose another admin menu option to navigate away from the page I’m editing that’s locking it up):
- Firefox: Loading icon keeps spinning in both regular and private but full screen locks up in both regular and private. Eventually both say “This page is slowing down Firefox. To speed up your browser, stop this page.”
- Brave: Loading icon and full screen lock up in both regular and private.
- Chrome: Loading icon and full screen lock up in both regular and incognito.
- Edge: Private is the only one where the pattern actually loaded and the full screen didn’t lock up. (Edge regular the loading icon and full screen both locked up.)
I didn’t see any messages in the console on any of the browsers.
Does that give you any hints about what might be going on?
Actually, I don’t know if this helps or just confuses things more, but…I just took it a step further to try something out. The same pattern is repeated multiple times on multiple pages. On the one page I was using to check this out (where I was able to see the first synced pattern on the page in Edge (private)), I detached the pattern. After I did that, the rest of the synced patterns on the page (still synced) showed/the screen didn’t lock up anymore — it’s okay in Edge (private), and also okay when I check in Brave (regular).
However, I tried going to a different page in Edge (private), and it was still locking up there (and the loading icon wasn’t spinning) — it didn’t load okay like the first page did previously when in Edge (private). So I’m still/even more confused about what’s going on.
Thanks for any thoughts.
Same problem for me but the issue affects synced blocks that have WPForms in them. Synced patterns with other content are fine. Also non-synced patterns with WPForms are ok.
But a synced pattern with a WPForms form in them cause the editor to hang. When I then stop the page I get:
Error code: RESULT_CODE_HUNG
Same thing here, Any page with a Pattern get locked up. Not specific you one site I have a few sites that this happens on
Thread Starter
bdd
(@bws-online)
Still seeing this with WP 6.6 (or 6.6.1). Rolling back to 6.5.5 eliminates the issue.
A simple synced pattern (a Kadence Row Layout block with a background image in it) is demonstrating the issue. Kadence support mentioned seeing the issue from other people, not just me.
Having the same issue on our site as well. We also have Kadence installed and are unable to edit posts that have a synced reusable block.
I’m having the SAME problem! It’s only happening on synced blocks. I can’t even unsync it since the admin completely freezes when I open those pages! Still looking for a solution.
I’ve had an exchange today with a plugin developer who I highly respect – and has always been extremely honest about his code performance – and this is what he told me:
“So there is currently an issue that was introduced in WordPress 6.6 that is causing certain custom blocks including ours to crash when you try and add them to a custom synced pattern.
We’re looking more into this to see if there is a way we can solve it from our end, but a few active threads I’ve found point to it being a bug in WordPress core that will be fixed in an update, but that’s where we’re at for the moment, as we are still testing things on our own dev sites.”
Hopefully, WordPress will acknowledge this issue and fix it from their end.
-
This reply was modified 1 year, 2 months ago by
tbream.
I am not sure whether this is the issue in question, it seems relevant. If so, perhaps it will be fixed in 6.7
https://github.com/WordPress/gutenberg/issues/63909
Thread Starter
bdd
(@bws-online)
6.7.2 and it just happened again. I thought it was fixed already.
ETA: Had to rollback to 6.6.2 to be able to edit my content.
-
This reply was modified 8 months, 1 week ago by
bdd.