You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This adds 3 tests to reproduce the behavior under large payload volume:
# failing workerd case using one shared WebSocket session under large payload volume
pnpm test -- --project workerd __tests__/workerd.test.ts -t "fails with a shared websocket session"# passing workerd control using fresh WebSocket sessions per batch
pnpm test -- --project workerd __tests__/workerd.test.ts -t "passes with a fresh websocket session per batch"# passing Node control using the same shared WebSocket session pattern
pnpm test -- --project node __tests__/index.test.ts -t "same high-byte-volume workload in Node"
For the failing test, you should see something like this:
[vpw:info] Starting isolated runtimes for 1...
<--- Last few GCs --->
[16746:0xbf21f4000] 1353 ms: Mark-Compact 1399.4 (1423.0) -> 1399.4 (1423.0) MB, pooled: 2.2 MB, 2.02 / 0.00 ms (average mu = 0.113, current mu = 0.000) allocation failure; GC in old space requested
[16746:0xbf21f4000] 1355 ms: Mark-Compact 1399.4 (1423.0) -> 1399.4 (1423.0) MB, pooled: 2.2 MB, 2.02 / 0.00 ms (average mu = 0.060, current mu = 0.001) allocation failure; GC in old space requested
workerd/jsg/setup.c++:38: fatal: V8 fatal error; location = Ineffective mark-compacts near heap limit; message = : allocation failed: JavaScript heap out of memory
*** Received signal #6: Abort trap: 6
stack: 19b073887 19af7884f 1038d1f0f 103d0c18b 103ee937f 103ee765b 103efb6a3 103efb42b 103efaf47 103ed0cb7 103fe8cfb 103fef2ff 103fef3eb 103fef3eb 103fe86db 103fe8417 103d85a23 103bd960b 170286f8f 103b75983 103c50977 103b6601b 103b3addb 103e550cf 103e559ab 103e55aeb 103e6b10f 103e6af7b 1038aa7cf
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
TypeError: fetch failed
❯ node_modules/.pnpm/undici@7.18.2/node_modules/undici/index.js:127:13
❯ process.processTicksAndRejections node:internal/process/task_queues:105:5
❯ MessagePort.<anonymous> [worker eval]:28:22
Caused by: Error: connect ECONNREFUSED 127.0.0.1:55534
❯ TCPConnectWrap.afterConnect [as oncomplete] node:net:1637:16
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.
I have read the CLA Document and I hereby sign the CLA
You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to #158
This adds 3 tests to reproduce the behavior under large payload volume:
For the failing test, you should see something like this: