Issue Summary

When a page has a high quantity of certain types of JPG, SVG or WEBP images, inside of a table or just pasted in the page, these attachments can make the page to take much time for load or display an error after 52 seconds (timeout).

Steps to Reproduce

1. Create a page
2. Insert around 30 SVG images (tested with ~300KB SVG)
3. Publish the page

Expected Results

• The page should load without problems

Actual Results

• The page takes much time to load its contents or, after 52 seconds, it will display an error similar to the following one:

  Something went wrong

  Try refreshing the page. Refresh
  If the problem persists, contact Atlassian Support or your space admin with the following details so they can locate and troubleshoot the issue:

  • This code: ce3oe7
  • The URL of this page * Reload this page
• The following error is thrown at the browser's console:

  Error: GraphQL error: Exception querying the remote GraphQL service: java.net.SocketTimeoutException: 52,000 milliseconds timeout on connection http-outgoing-538743 [ACTIVE]
      at new t (bundle.esm.js:63)
      at t.getQueryResult (react-hooks.esm.js:269)
      at t.i.getExecuteResult (react-hooks.esm.js:73)
      at t.execute (react-hooks.esm.js:106)
      at v (react-hooks.esm.js:380)
      at d (react-hooks.esm.js:354)
      at v (react-hooks.esm.js:397)
      at nt (ContentBody.js:124)
      at $i (react-dom.production.min.js:153)
      at Da (react-dom.production.min.js:175)

• And this is the failing request:

  Request URL: https://INSTANCE.atlassian.net/cgraphql?q=QueryPreloader_ContentQuery
  Request Method: POST
  Status Code: 200 
  
  Response:
  {"errors":[{"message":"Exception querying the remote GraphQL service: java.net.SocketTimeoutException: 52,000 milliseconds timeout on connection http-outgoing-538743 [ACTIVE]","locations":[{"line":1,"column":122}],"path":["content"]}],"data":{"content":null}}

Notes

This usually happens with SVG and WEBP images but it was also noticed with certain types of JPG files.

Workaround

There're two possible workarounds for this bug:

• Split the page into multiple pages containing less images
• Convert the images to PNG as this bug doesn't seem to be caused by those types of images