Erik Dubbelboer
Erik Dubbelboer
The problem is that at this point you don't have a URL. It could happen at any point in the request cycle where maybe the URL hasn't been received yet....
When shutting down idle connections are just closed. This is normal. Since there is no request there is also nothing to respond with `Connection: close` to. The error you are...
Having the idle connections be closes right away or with a timeout will just give the same results. Http clients should always be able to handle idle connections being closed...
The error is not with `fasthttp`, the error is with the upstream server that can't handle the load or with this proxy not configuring the `fasthttp.Client` correctly for this use....
@cassianotartari In your universal HTML you still seem to have `myuserloginindisqus`. Is that something that doesn't matter?
Since webgpu is disabled I don't see this issue anymore. I'll try enabling webgpu again after the next release to see if it still happens and if I can pinpoint...
I ran the `preference: 'webgpu'` build again for a day. It's less than 1% of the users, but they are still affected: ``` TypeError: Cannot read properties of null (reading...
Firefox and Safari is because it only happens in `webgl` and this game has `preference: 'webgpu'`. Now that I removed the preference it also happens in Chrome with webgl.
Yes, removing the blur filter fixes it. I'm just doing: ```js const filter = new BlurFilter({ strength: 2, quality: 4, }); this.filters = [filter]; ``` Where `this` is a `Container`...
@GoodBoyDigital what do you mean with the "current release", cause v8.1.0 is 3 weeks old and still has this issue?