Excellent, thanks for sending these in! We’ll take a look and follow up with next steps after we’ve opportunity to make sense of the logs.
We’ve been digging through these logs and unfortunately are not coming up with much to aid us. Based on all the work done up to this point, it does seem clear that the issue is specific to something about your particular macbook/environment. At least half of our dev team is using macbooks, so we know it’s not a general OS/Hardware issue.
I’d like to try one other thing to rule out possible bugs in how we are interacting with the browser engine.
Go ahead and update your designer launcher JVM flags to include the following, (along with the flags we previously set for the log files, in memory cache, and increased designer memory):
-Dperspective.browser.mode.lightweight=true
-Djxbrowser.ipc.external=true
These flags change how the browser is loaded in the designer when running on macOs by altering the way the process executes in the native operation system. After saving this configuration, go ahead and try relaunching the designer and try creating a perspective View.
Note that these flags are purely diagnostic, and will in fact prevent the perspective view designer from functioning correctly. You will not be able to add components to the view with these settings. Our goal here is simply to see if these settings allow a view to be created, opened and closed.
If this changes behavior, we have a route to investigate. If it doesn’t, then we’re going to have to start looking more specifically at your device: what applications are installed, running, what kinds of security settings/antivirus/network software, etc.
For now, let’s see what insight these additional flags provide.
Well, here is the surprise. I added those flags, and was able to open, modify, save, and reopen a view.
Thanks for notifying us with your result, this gives us a path to investigate. No guarantee it’ll result in a solution we want, but we’ll dig in and see if we can get some answers.
@NorthPoint
Okay, we’re going to keep trying some things on our end to at least make this experience better for you. In the meantime, could you do one more thing on your system for me? Remove the extra flags added in Perry’s last post (at least, temporarily) and then launch the designer again. Assuming you get back into the broken state, follow the instructions here to get a thread dump from the JVM. In talking with the browser vendor, they’re thinking that the root cause may be a threading/deadlock issue.
Thanks for all your help getting this information to us.