Hi Anders,

We found out an potential issue with SCOOP and evaluation of once features combined with process/region impersonation.
We'll be working to fix this SCOOP issue, this may be the cause of your trouble, or not. I haven't been able to reproduce yet your issue, so I can not ensure this would fix your issue.
For this SCOOP issue, turning off the GC would be a workaround, however if your application is using a lot of object, this will not be a good solution in the long term.

What you could also try, if to use "thread" concurrency. If you don't use yourself SCOOP directly, the EiffelWeb standalone can be compiled and executed with any concurrency mode.

What would help us to reproduce your issue, is to have a reproducible example, or even a virtual machine image to reproduce it.
If possible, providing your source code would help, so we could try to reproduce the issue locally.
So any solution that would allow us to reproduce the issue would really help, especially if it can takes a few days of execution to reproduce.