Problem with Activiti Modeler in Chrome

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-11-2014 06:48 PM
When starting a new diagram, the second item pulled onto the canvas (or the second item added via the menu items when hovering over the first item added) will display the message "Aw snap! Something went wrong while displaying this webpage." The only resolution is close the browser window and restart Activiti Explorer.
This happens about 80% of the time when adding a second element to the canvas. This never happens when adding the first element, or any subsequent element if the addition of a second element is successful. Furthermore, any existing diagram does not produce this problem no matter how many items are added. Finally, if I add a single element, save, exist, then edit, I can get around the issue as well.
Additionally, this does not occur when using Firefox. I have tried this on several machines, several different activiti instances (both local and remote), and have cleared all browser cache.
Any ideas on why this would occur or any solutions?
Thanks,
K
This happens about 80% of the time when adding a second element to the canvas. This never happens when adding the first element, or any subsequent element if the addition of a second element is successful. Furthermore, any existing diagram does not produce this problem no matter how many items are added. Finally, if I add a single element, save, exist, then edit, I can get around the issue as well.
Additionally, this does not occur when using Firefox. I have tried this on several machines, several different activiti instances (both local and remote), and have cleared all browser cache.
Any ideas on why this would occur or any solutions?
Thanks,
K
Labels:
- Labels:
-
Archive
1 REPLY 1

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2014 01:05 PM
Yes, there's a bug in Chrome 32 that is causing this issue. So in Firefox it's working ok.
We should fix this in the Modeler code however, can you create a JIRA issue?
Thanks,
We should fix this in the Modeler code however, can you create a JIRA issue?
Thanks,
