Memory access violation leads to different outcomes in different envrionments about isolate HOT 2 CLOSED

The code is indeed incorrect: erase on an unordered_map is documented to invalidate iterators.

It's hard to tell what exactly happens. Different container managers can set up control groups in different ways (which is why it is not recommended to run Isolate in containers). Additionally, you have address space randomization turned on, so the behavior is likely not deteriministic.

Are you using the same system (compilers, libraries, etc.) in both scenarios?

from isolate.

@gollux Thanks for looking into this.

Are you using the same system (compilers, libraries, etc.) in both scenarios?

Yes, the same Docker image is used in both scenarios.

Since applying the address space size limit works, this is no longer issue. I just wanted to make sure this is not a sandboxing bug, which it doesn't seem to be.

from isolate.