IDE Lockups 9.6.0 on Mac
Posted: Mon Jul 06, 2020 9:43 am
Hi,
I am working on a project that contains several sub stacks and from time to time the IDE code editor locks up and/or a save dialog refuses to close. All these issues are hard to replicate making a bug report difficult to write.
I wonder if others have experienced anything similar?
In the case of my project the main stack is a palette stack and I wonder if this status causes the IDE some issues. Also my palette stack opens sub-stacks and then adds new cards. These sub stacks are not palette stacks.
My palette stack closes the sub-stack which I think triggers a "save stack" warning and this may be the root cause of the problems with the code editor. The specific problem is that the editor freezes and clicking on the window close icon prompts the property inspector to open showing details of a control. This fault has the feel of an internal pointer problem but thats above my pay grade! Other parts of the IDE still work and its possible to request that some code is edited and this action unlocks the freeze.
None of the above is repeatable, but seems to occur once every twenty minutes or so.
As a side question is what exactly happens when a sub-stack is closed ? By definition a sub-stack is part of the parent stack file so it is not removed from memory until the parent stack is closed. So I wonder if it may be safer for me to just to hide my sub-stacks thus preventing any save dialogs from being posted.
I am interested in any similar reports or ideas.
I am working on a project that contains several sub stacks and from time to time the IDE code editor locks up and/or a save dialog refuses to close. All these issues are hard to replicate making a bug report difficult to write.
I wonder if others have experienced anything similar?
In the case of my project the main stack is a palette stack and I wonder if this status causes the IDE some issues. Also my palette stack opens sub-stacks and then adds new cards. These sub stacks are not palette stacks.
My palette stack closes the sub-stack which I think triggers a "save stack" warning and this may be the root cause of the problems with the code editor. The specific problem is that the editor freezes and clicking on the window close icon prompts the property inspector to open showing details of a control. This fault has the feel of an internal pointer problem but thats above my pay grade! Other parts of the IDE still work and its possible to request that some code is edited and this action unlocks the freeze.
None of the above is repeatable, but seems to occur once every twenty minutes or so.
As a side question is what exactly happens when a sub-stack is closed ? By definition a sub-stack is part of the parent stack file so it is not removed from memory until the parent stack is closed. So I wonder if it may be safer for me to just to hide my sub-stacks thus preventing any save dialogs from being posted.
I am interested in any similar reports or ideas.