The Jade 2025 release focuses on modernising the developer experience and helping you build faster, smarter, and more scalable applications.
When a LockException is raised you have access to the process that is locking the targetted object.
Exception :: targetLockedBy (Process)
If you try and call 'getCallStackInfo' on this process you get an exception "1265 (Environmental object operation is out of scope for process)" - I'm not sure why there is this restriction in place when you can simply get the call stack from JadeMonitor on any process.
Knowing what the locking process is doing to lock the object would make our lives debugging this a lot better.
Sam Stokell
