Really good discussion everyone (with the exception of some almost-personal attacks - and one actual personal attack that I removed, as moderator). All of this needs to be heard ... both the technical failings - as well as the emotional and time/cost/profit impact.
This Community is seen by Graphisoft, but is not a tech support channel. Hopefully at some point a GS employee will join in to let everyone know that these issues are in the system. What I originally asked for seems impossible from what I've read... a reproducible example to assure a quick escalation to a bug fix via normal tech support reporting. But, I think the more anecdotal experiences are reported for this seemingly random issue, the more helpful this thread will be towards reaching a solution.
I know several of you are not just experts, but are very well-recognized experts (since as moderator I can see who you really are) and if @4dProof and @DGSketcher cannot reproduce this, then I suspect nobody can.
An aside...to those who have done some programming in GDL etc and think this kind of bug should be easy to find, I would just point out (with my computer scientist hat on this time) that ARCHICAD has been multi-threaded for many years now ... and has become more multi-threaded with each version in order to satisfy user demands for speed. Sequential programming, such as GDL, is relatively trivial to debug...because the potential sequence of events is very limited. When concurrency is added to the mix as in the hundreds of threads in ARCHICAD, each doing some different portion of a task - or even totally different tasks - background updating, generating different parts of a model view, etc - so much work is never done in a predictable order and the potential interaction of different threads accessing the same data (MVO perhaps in this case) is also somewhat random. The protection of data access/update and sequentialization when necessary (e.g., an MVO update by a user when the background tasks are generating drawings based on that MVO) to shared data is key and is critical to bug-free multi-threaded code. Robust multi-threaded programming is a high level skill for programmers. These things can be really hard to track down because of the seeming randomness (due to billions of possible overlapping code execution paths).
Please do continue to share both whether the issues of the OP occur to you, and if possible, as some have done, what your most recent actions were prior to seeing things go wonky. 🙂
One of the forum moderators
AC 26 USA and earlier • macOS Ventura 13.4, MacBook Pro M2 Max 12CPU/30GPU cores, 32GB