• Resolved simk1

    (@simk1)


    After upgrading to WordPress 6.6 issues in the editor starting to occur when accessing pages which include “synced pattern”. After opening a page which includes a synced pattern, the browser (Firefox) displays the “browser is slow” Message with the button for cancelling the related javascript.

    The same issue occurs when trying to add an existing synced pattern into a new page. When trying to select the pattern the browser hangs.

    After cancelling the related script the following stacktrace can be seen in the console:


    Script terminated by timeout at:
    s@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:13212
    rt@https://domain/wp-includes/js/dist/core-data.min.js?ver=07feee0ca98b13ab617d:2:36004
    r@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:16845
    i@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:17349
    qd@https://domain/wp-includes/js/dist/editor.min.js?ver=8607251058f984a77c8f:14:1734
    Oe</<@https://domain/wp-includes/js/dist/block-editor.min.js?ver=f9506c5f13cc3995ed19:21:111157
    r@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:9528
    r@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:16845
    oe/<@https://domain/wp-includes/js/dist/block-editor.min.js?ver=f9506c5f13cc3995ed19:21:104194
    Tn/<@https://domain/wp-includes/js/dist/block-editor.min.js?ver=f9506c5f13cc3995ed19:21:126064
    s@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:13089
    r@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:9528
    r@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:16845
    @https://domain/wp-includes/js/dist/block-editor.min.js?ver=f9506c5f13cc3995ed19:21:519544
    Je/</p/p<@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:9:2046
    __unstableMarkListeningStores@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:22094
    me/a</<@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:22352
    p@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:9:2010
    getValue@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:9:2670
    zu@https://domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:63078
    551/_u/<@https://domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:63009
    s@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:9:2266
    c@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:9:2292
    me/c/o.subscribe/r<@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:20667
    be/instantiate/<@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:18995
    v@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:8167
    k/</</<@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:11061
    a/</</<@https://domain/wp-includes/js/dist/redux-routine.min.js?ver=a0a172871afaeb261566:9:750
    U/</<@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:10641
    D/</</<@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:10999
    be/instantiate/p/<@https://domain/wp-includes/js/dist/data.min.js?ver=7c62e39de0308c73d50c:2:16389
    Pk/<@https://domain/wp-includes/js/dist/block-library.min.js?ver=96b614e020e4ab48838d:4:473467
    Pk@https://domain/wp-includes/js/dist/block-library.min.js?ver=96b614e020e4ab48838d:4:473409
    Pk/<@https://domain/wp-includes/js/dist/block-library.min.js?ver=96b614e020e4ab48838d:4:473482
    Pk@https://domain/wp-includes/js/dist/block-library.min.js?ver=96b614e020e4ab48838d:4:473409
    Rk/<@https://domain/wp-includes/js/dist/block-library.min.js?ver=96b614e020e4ab48838d:4:474563
    ri@https://domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:93198
    Ss@https://domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:113322
    551/ws/<@https://domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:112062
    ws@https://domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:112127
    is@https://domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:105883
    Hl@https://domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:46663
    551/rs/<@https://domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:103288

    The issue does only seem to affect the ability to edit pages – users which are not logged into the wordpress site do not seem to be affected.

    Reverting to 6.5.5 fixed the issue.

Viewing 15 replies - 1 through 15 (of 21 total)
  • I also have the same problem, I get the error: RESULT_CODE_HUNG

    Moderator James Huff

    (@macmanx)

    This problem may be a plugin or theme conflict. Please attempt to deactivate all plugins and switch to the default Twenty Twenty-Three theme. If the problem goes away, re-activate them one by one to identify the source of the problem.

    If you can install plugins, install Health Check. On the troubleshooting tab, you can click the button to deactivate all plugins and change the theme for you while you’re still logged in without affecting normal visitors to your site.

    Hi, same issue here on multiple websites, on all browsers (MacOS Chrome / Firefox latest releases).

    Everything was working fine before updating to 6.6.

    Moderator James Huff

    (@macmanx)

    Not for me though, so please try the troubleshooting steps above.

    Thread Starter simk1

    (@simk1)

    The issue seems to be related to the Editor Plus (v2.10.0) plugin (https://ww.wp.xz.cn/plugins/editorplus/).

    I manged to reproduce this issue with the following:

    – a clean WP 6.6 Installation
    – GenerateBlocks Version 1.9.1
    – GP Premium Version 2.4.1 (paid version)
    – using the GeneratePress Theme

    Using this I get a “normal” error message popup:
    “The editor has encountered an unexpected error”

    ts@domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:102636
    Ku@domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:65625
    be/<@domain/wp-includes/js/dist/compose.min.js?ver=b8d54449305350b51869:9:31719
    ri@domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:93198
    Ss@domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:113322
    551/ws/<@domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:112062
    ws@domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:112127
    is@domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:105883
    Hl@domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:46663
    551/rs/<@domain/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.3.1:2:103288


    Now if I also throw WPCode Lite (Version 2.2.9) and Essential Blocks (Version 4.8.2) into the mix,
    the hanging issue occurs.

    I got the same problem after upgrading to 6.6.

    Webpages stop responding added a synced pattern, by click or drag, through post editor. Un-synced patterns is working fine.

    Synced patterns also keep loading content in post editor while editing existing posts.

    • This reply was modified 1 year, 9 months ago by ikyent.
    Moderator James Huff

    (@macmanx)

    Ok, please try the troubleshooting steps above.

    Hi, encountered similar issues with other plugins (like SimpleTOC) and synced patterns. But also synced patterns without any specific plugin blocks.

    Feels like a WP 6.6 issue, which remains unfixed in 6.6.1 as far as I can tell… 🙁

    yes, the plugin Health Check helps. for a temp fix, just turn the maintenance on, everything would be fine.

    1. This issue persists in both WordPress 6.6 and 6.6.1.
    2. I installed and ran the Health Check plugin as instructed and that did not provide help with the issue.
    3. As noted in the console message from the OP react-dom.min.js is showing up as a potential issue. I’m assuming this is why the whole DOM hangs-up.
    4. I was able to successfully avert the issue by running define('SCRIPT_DEBUG', true); in my wp-config.php. This is fine for local testing, but it’s definitely not a viable solution for production.

      Can we please re-open this ticket until the problem is resolved? Or can you point me to the active ticket for this issue?

    I’ve noticed that even when the editor does not hang when using synced patterns in general it is MUCH slower than under WP 6.5. Adding define('SCRIPT_DEBUG', true); does seem to help a little, but not much…

    These Github tickets for Gutenberg are about performance degradation:

    Can confirm, am getting this behavior too. Happens on synced blocks. We’re getting this console error:

    block-editor.js?ver=2cb36d67922bfdc27a1d:17605 Warning: Maximum update depth exceeded. This can happen when a component calls setState inside useEffect, but useEffect either doesn't have a dependency array, or one of the dependencies changes on every render.
    at BlockProps (https://redacted.lndo.site/wp/wp-includes/js/dist/block-editor.js?ver=2cb36d67922bfdc27a1d:17599:3)

    Thank you for confirming the issue. We’re experiencing the same behavior with synced blocks, and the console error you’ve mentioned is consistent with what we’re seeing. The “Maximum update depth exceeded” warning suggests that there might be an issue with the useEffect hook in the BlockProps component. It seems like setState is being triggered in a way that’s causing an infinite loop, potentially due to missing or constantly changing dependencies in the dependency array. We’ll need to look into the component’s logic to identify and resolve this.

    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/pattern.

    Edit: Rolling back to WordPress 6.5.5 fixed the issue for us.

    • This reply was modified 1 year, 7 months ago by kraisor.

    @macmanx has this been fixed? It’s unclear to me whether it is being tracked on gutenberg core. Is this the related issue? https://github.com/WordPress/gutenberg/issues/63909

    I’m surprised that it is not a higher priority, as it does seem core related. Downgrading to 6.5 is not a feasible long term solution of course.

    Many thanks!

Viewing 15 replies - 1 through 15 (of 21 total)

The topic ‘WP 6.6 hangs on synced pattern’ is closed to new replies.