@Johnathan - Unfortunately, this error is not graphite specific... rather, it is an error in wasm sandbox setup in some environments. It occurs even before we load the graphite code. I tested the sandbox creation code path on my machine by visiting the graphite micro-benchmark you had sent earlier... My best guess right now (based on the fact that we are seeing different behavior in different environments) the wasm sandbox runtime is assuming behavior that certain OS kernel combinations may not provide or perhaps there is some interatcion of the linux sandbox, wasm runtime and os kernel versions... I will look into this further. For now, I have submitted a fix that just disables IO redirection.
Bug 1606981 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
@Johnathan - Unfortunately, this error is not graphite specific... rather, it is an error in wasm sandbox setup in some environments. It occurs during sandbox creation, but before we load the graphite code. I tested the sandbox creation code path on my machine by visiting the graphite micro-benchmark you had sent earlier... My best guess right now (based on the fact that we are seeing different behavior in different environments) the wasm sandbox runtime is assuming behavior that certain OS kernel combinations may not provide or perhaps there is some interatcion of the linux sandbox, wasm runtime and os kernel versions... I will look into this further. For now, I have submitted a fix that just disables IO redirection. Fwiw, I will also try your suggested approach to see what happens.