Now, regarding the particular issue you're complaining about. I've spent countless hours and days looking into it, but just can't reproduce it here. If I could easily reproduce it, things would have been a lot easier to debug.
thanks for clarification and thanks for your work (over years, I need to mention).
it's the first time that *I* read that an involved developer is aware/working or was working on the issue.
I didn't really believe the issue was undergone, but no one really knew that, until now.
maybe former communication would have lowered the complains/frustrations.
some pages back you will find my bug report regarding that issue and also my offer helping to nail the bug down, but I got no response.
Okay, I said to myself - with an slightly feel of being ignored  - : the dev's might be overloaded releasing 18.1 ... -
anyway, I've tested @side's Optimized 18.1 for some days and it seems the issue doesn't exist there and so I'm confident it won't in your upcoming Official 18.1.
and here is the key where the harshness of warrantable complains starts to grow.
unable to reproduce the bug and unable to fix the bug are both the same frustration on different sides (dev, user).