Repository navigation
fix: clear timeout when turbo-stream encoding completes - #14735
Conversation
🦋 Changeset detectedLatest commit: 1ebbd8f The changes in this PR will be included in the next version bump. This PR includes changesets to release 11 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Hi @mcollina, Welcome, and thank you for contributing to React Router! Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once. You may review the CLA and sign it by adding your name to contributors.yml. Once the CLA is signed, the If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at hello@remix.run. Thanks! - The Remix team |
|
Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳 |
|
question: Could this interact with I'm wrestling with high memory usage and keep coming across timers and streams in the heapsnapshots, wondering if this might be related. |
|
We've had a memory leak issue on persistent node servers that seems to be resolved mostly after adding the following as a patch, not sure if it's related, was still profiling the patch ourselves before opening an issue. requestSignal.addEventListener("abort", () => clearTimeout(timeoutId), { once: true });We also use AsyncLocalStorage, so might be somewhat related? |
Yes, this is it. |
|
Thanks @jacob-ebey! |
|
oops - this should have gone to |
…)" This reverts commit 44991a9.
|
🤖 Hello there, We just published version Thanks! |
|
🤖 Hello there, We just published version Thanks! |
No description provided.