Summary

If one user is editing a Page and another user adds a Gliffy diagram to the page with the Copy Gliffy Diagram option to an existing page context the page crashes out and encounters 400 bad request errors whenever attempting to apply an update from a chrome browser

Environment

• Discovered on EAC (Confluence 6.7.0)
• Chrome Version 63.0.3239.84 (Official Build) (64-bit)

Steps to Reproduce

1. User A enters edit mode on a page
2. User B on an alternate page containing a Gliffy Diagram selects the Copy Diagram option
3. User B added diagram to Existing Page and selects the page user A is editing
4. Save

Expected Results

Gliffy Diagram is added to the page

Actual Results

• User A encounters timeout error on screen
• The Gliphy diagram is applied to the page
• Entering edit mode the Gliphy diagram dissapears and shows 400 errors in javascript console
• Applying any update to the page 302 errors occur and updates time out
• Cannot revert changes on the page or the same 302 issue occurs

Notes

This does not happen in firefox, and issue can be bypassed using the alternate browser but Chrome will continue to encounter errors

Workaround

Solution relates to Gliphy Troubleshooting page

• As User B
  • Navigate to "chrome://flags" in a chrome browser
  • Disable 2D canvas hardware acceleration
  • Flush Browser cache
  • Restart chrome
• Navigate back to the edited page
• Edit the page and make any change
• Update the page

Gilffy diagram is removed but other users in chrome can now apply edits to the page without encountering the error, re-add the diagram and you can then re-enable the 2d acceleration option in chrome.