(In reply to Lars T Hansen [:lth] from comment #8) > Ryan, is this program supposed to do something, if it doesn't crash? It's an early attempt at running [Seshat](https://github.com/matrix-org/seshat) (a Matrix message index for searching) in the browser. At the moment, it does not do much beyond printing a few "Seshat" prefixed messages to the console, but it's possible you might not even see those, as seems to trigger other Firefox-specific Wasm issues related to too many threads allocating too many `WebAssembly.Instance`s. I guess that's a long way of saying it might have further unrelated issues, so for the purposes of this bug, as long as it doesn't crash, that seems like success to me. (Sorry it's not the easiest test case to work with... I wasn't sure which parts were necessary to trigger the problem.)
Bug 1681724 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Lars T Hansen [:lth] from comment #8) > Ryan, is this program supposed to do something, if it doesn't crash? It's an early attempt at running [Seshat](https://github.com/matrix-org/seshat) (a Matrix message index for searching) in the browser. At the moment, it does not do much beyond printing a few "Seshat" prefixed messages to the console, but it's possible you might not even see those, as it seems to trigger other Firefox-specific Wasm issues related to too many threads allocating too many `WebAssembly.Instance`s. I guess that's a long way of saying it might have further unrelated issues, so for the purposes of this bug, as long as it doesn't crash, that seems like success to me. (Sorry it's not the easiest test case to work with... I wasn't sure which parts were necessary to trigger the problem.)