Gunter Spranz
Gunter Spranz
Doesn't seem to be the same memory leak though (string, concatenated-string)
And this leak is still there when I remove the useExecutionCancellation plugin. I continue adding more dependencies now.
I didn´t have much time, but today I made a little experiment. I started my server and made a few simple queries. I put break points in the execute function...
A little bit debugging more, after 6 requests: Indeed, the same signal is used every time and the listeners are piling up.
Btw, the stack trace is veeery long to this place here, but I saw batching (which I activated) and some proxying stuff (I use stitching) on the way down, maybe...
Yeah, hopefully I have some time later today
So I started the yoga-server.ts in the execution-cancellation directory manually with `node --import tsx yoga-server.ts` and made some requests. I noticed that here too it never called signal.removeEventListener. So, in...
I am getting close :) I put the following debugging code directly into execute.js: and of course a `let lastSignal = null` at the beginning of the module. When I...
I'll try to play around and add more stuff to the test yoga-server.ts, maybe I find the reason of the shared signal. Btw, here is how I create the yoga...
I added some of those options to the test yoga-server in the exection cancellation test directory, but he still doesn´t re-use the signal. It also doesn´t happen when I add...