Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-20671

Using a Kanban board results in error: ResizeObserver loop limit exceeded

      Issue Summary

      Using a Kanban board results in error: ResizeObserver loop limit exceeded.

      The ResizeObserver is a component for rendering, that exists only on the browser side, so this error can be safely ignored.

      Steps to Reproduce

      1. Open a Kanban board.
      2. Select a task.
      3. Make a typo in a text field so Grammarly recognizes it and hover the cursor over it
        OR
        Just hover the mouse over the Grammarly icon in the lower right of any text field while editing it.

      Expected Results

      No errors happen.

      Actual Results

      The error described above happens.

      Note

      The problematic Chrome extensions that have been identified so far are:

      Workaround

      Use another browser or disable Chrome Grammarly extension.

            [JSWSERVER-20671] Using a Kanban board results in error: ResizeObserver loop limit exceeded

            We have the same problem in Jira Data Center 9.17.4

            Kalle Narinen added a comment - We have the same problem in Jira Data Center 9.17.4

            We have the same problem in Jira Data Center 9.14.1

            Andrea Maria Loi added a comment - We have the same problem in Jira Data Center 9.14.1

            김상범 added a comment -

            same issues when using extention that Horizon HTML5 Redirection 
            https://chromewebstore.google.com/detail/horizon-html5-redirection/ljmaegmnepbgjekghdfkgegbckolmcok?hl=en

             

            김상범 added a comment - same issues when using extention that Horizon HTML5 Redirection  https://chromewebstore.google.com/detail/horizon-html5-redirection/ljmaegmnepbgjekghdfkgegbckolmcok?hl=en  

            Keith added a comment - - edited

            The bigger the customer the bigger the impact from this"low" priority bug.
            Thankfully we run a data center configuration with a node in reserve AND thankfully we designed a self monitoring tool that takes an impacted node out of load balancer rotation.
            If we had not engineered our own solutions to fill the large longstanding gaps in Jira's backend we would likely have had a cascading failure that could have caused a total site outage.

            A overwhelming majority of our page load errors are from Chrome users.
            A fact we also have to use a 3rd party tool to even identify in real time.

            All of Atlassian please consider reality when you are typing the "workarounds"
            Eventually our "workaround" will be to stop using Atlassian products.

            Keith added a comment - - edited The bigger the customer the bigger the impact from this"low" priority bug. Thankfully we run a data center configuration with a node in reserve AND thankfully we designed a self monitoring tool that takes an impacted node out of load balancer rotation. If we had not engineered our own solutions to fill the large longstanding gaps in Jira's backend we would likely have had a cascading failure that could have caused a total site outage. A overwhelming majority of our page load errors are from Chrome users. A fact we also have to use a 3rd party tool to even identify in real time. All of Atlassian please consider reality when you are typing the "workarounds" Eventually our "workaround" will be to stop using Atlassian products.

            Jakob KN added a comment - - edited

            Support confirmed to me that this bug is also causing the error shown below.
            The error happens when creating an issue while viewing a kanban/scrum screen, while the LastPass extension is active in Chrome.

            In our organization, and many others i assume, the LastPass extension is required and can not be disabled by users. Which means there's no available workaround. 
            This is eventually going to affect our entire userbase and it's not really viable to run a Jira instance where users get error messages whenever viewing boards or creating issues. 

            This is happening in both our production (8.20.12) and staging (9.4.6) instances.

            If we can bump up the priority on this it'd be much appreciated.
            This bug has been around since 2020 after all.

             

            An error occurred
            Please try refreshing the page, or contact your administrator / Atlassian Support if the problem continues.

            Details

              • Exception: ResizeObserver loop completed with undelivered notifications.
              • Resource: https: //jira.XXXXX.com/secure/RapidBoard.jspa?rapidView=XXX&projectKey=XXXX
              • Line: 0
              • Column: 0

                Environment

            Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36

            Jakob KN added a comment - - edited Support confirmed to me that this bug is also causing the error shown below. The error happens when creating an issue while viewing a kanban/scrum screen, while the LastPass extension is active in Chrome. In our organization, and many others i assume, the LastPass extension is required and can not be disabled by users. Which means there's no available workaround.  This is eventually going to affect our entire userbase and it's not really viable to run a Jira instance where users get error messages whenever viewing boards or creating issues.  This is happening in both our production (8.20.12) and staging (9.4.6) instances. If we can bump up the priority on this it'd be much appreciated. This bug has been around since 2020 after all.   An error occurred Please try refreshing the page, or contact your administrator / Atlassian Support if the problem continues. Details Exception: ResizeObserver loop completed with undelivered notifications. Resource: https: //jira.XXXXX.com/secure/RapidBoard.jspa?rapidView=XXX&projectKey=XXXX Line: 0 Column: 0 Environment Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36

            Jaedo Aum added a comment -

            If this is a case that conflicts with Deepl, you can do the following as an exception.
            1. drag any location in the Jira site 
            2. Click the Chrome Deepl Extension's Settings menu that popup
            3. Disable "Show the DeepL icon for reading"

             

            Jaedo Aum added a comment - If this is a case that conflicts with Deepl, you can do the following as an exception. 1. drag any location in the Jira site  2. Click the Chrome Deepl Extension's Settings menu that popup 3. Disable "Show the DeepL icon for reading"  

            Grzegorz.Ryznar added a comment - - edited

            Grzegorz.Ryznar added a comment - - edited Same happens  with externsion from DeepL to Chrome: https://chrome.google.com/webstore/detail/deepl-translate-reading-w/cofdbpoegempjloogbagkncekinflcnj

              Unassigned Unassigned
              5fb7769fcbc7 Allan Gandelman
              Affected customers:
              40 This affects my team
              Watchers:
              33 Start watching this issue

                Created:
                Updated: