Jörg Plewe

Hi all! I'm far from being a build/test expert, so I run into an issue with testing code using a WebWorker created with the `ng generate web-worker` CLI tool. Running...

Wow ... that was quick. I tried the following w/o success. Something more to do? ``` // require('jest-preset-angular/ngcc-jest-processor'); module.exports = { // preset: "jest-preset-angular", preset: "jest-preset-angular/presets/defaults-esm", setupFilesAfterEnv: ["/jest.setup.ts"], setupFiles: ["jest-canvas-mock",...

Thank you so far ... I cannot find a difference. Using `--experimental-vm-modules` (which seems to be essential?) fails at a different place. I will try to create a WebWorker on...

Thx for the quick response... It can also be seen as a feature, just painting things on a canvas and automatically have it in a texture. Maybe an immutable-flag (or...

Sounds like "no way out"? Do you advise using WebGL then? In general? Is there a clear advantage of WebGPU elsewhere?

@GoodBoyDigital, issue is not solved, v8(webgl) still a lot slower than v7. 7s against 4s on my notebook. Is this reasonable?

My "edge case" even uses 100000 `Text`s (Symbols coming from a font). I think I did what you suggest prior to V8, when text caching was introduced. And I think...

Thinking to the future, using my current approach together with the re-alived `ParticleContainer` won't work anyway? Needing a Texture that I don't have now?

This helped and I could fix it. Dropping a major feature of v8 might be worth being mentioned in the announcement blog.

Tell me please ... when using `CanvasTextSystem.getTexture()` ... Is it ok to just `destroy()` a texture after use or do I need to `returnTexture()` (and *not* `destroy()`) it?