The point of the OS guard page is to give us a native stack overflow error in cases where the stack is too small. This is not needed for java threads which run their own stack overflow control (VM guard pages), so there we disable the OS guard pages explicitly to save memory and some cycles the OS would spend mprotecting.

However, for all non-java threads we explicitly set the OS guard page size. This assumes we know what the OS deems sufficient for guarding - which we do not.

It would be better and would more precisely express our intent to just leave the default OS guard page size alone - so leave it at default - for non-java threads.




Right now, we explicitly set