Tyler Hallada
513e95d697
After some testing, I'm fairly confident the issue I was seeing before isn't happening now. After re-processing ~250 plugins a few times with the same workers I was seeing significant slow-downs with large plugins. Also, if I was listening to music in the browser it would start crackling and popping. My hypothesis is that wee_alloc was causing a memory leak in the old version which was causing browsers to freak out unless I recreated the workers on every run. Though I'm not sure if that theory holds since I wasn't seeing out of control memory usage in the dev tools. Perhaps wee_alloc just wasn't good at managing memory after a certain number of allocate/deallocate cycles and was putting a huge strain on the browser. I'm hoping that reusing workers like this will also speed up processing and possibly resolve some crashing that some users were seeing. |
||
|---|---|---|
| .. | ||
| api.ts | ||
| games.ts | ||
| hooks.ts | ||
| logrocketSetup.ts | ||
| plugins.ts | ||
| store.ts | ||
| WorkerPool.ts | ||