Cannot run glpk.js on Firefox with nested webworker

[RaenonX]

I don't have a minimal reproducible example yet, but basically with the following setup:

- A webworker process ruinning a loop to run 10K times
  - In each loop, run glpk.js once

Chromium-based browser works fine. However, on Firefox, it just...doesn't return. I don't see any errors in the console unfortunately.

My setup is a bit complicated so it'll take some time to trim it down, if it's really needed, I can try creating a minimal example if I got time.

Thanks for reviving the project btw!

[jvail]

Maybe you can extend https://github.com/jvail/glpk.js/blob/master/test/mem.html where I tested parallel and successive runs to create a minimal test case for this. Do you have an async loop like for await...of? Does nesting mean you have a sub or shared worker?

[RaenonX]

Maybe you can extend https://github.com/jvail/glpk.js/blob/master/test/mem.html where I tested parallel and successive runs to create a minimal test case for this. Do you have an async loop like for await...of? Does nesting mean you have a sub or shared worker?

I'll see if I can find time try to make a minimal reproducible example, but strictly for await...of - no

But something like this...yes

export const actualCalc = async () => {
  await functionWrapperRunningLp();
}

export const branchingFunc = async () => {
  return actualCalc();
}

for (const cursor of enumerate()) {
  await branchingFunc(cursor);
}

Intentionally wrapped it 3 layers (actual is like 5~6) just in case because I don't know if that counts as for await...of and not sure if deep stack trace matters. Firefox just hates giving me any hints and Chromium works completely fine :/

[jvail]

OK, let me know when you have an example - my best guess is that it is a shared/sub worker thing that behaves differently in chrome vs firefox...