NotificationsYou must be signed in to change notification settings
Fork1k
Star11.1k

chore: downgrade msw and @radix-ui/dialog#20098

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

BrunoQuaresma merged 2 commits intomainfrombq/downgrade-msw

Oct 1, 2025

Merged

chore: downgrade msw and @radix-ui/dialog#20098

BrunoQuaresma merged 2 commits intomainfrombq/downgrade-msw

Oct 1, 2025

Conversation

Copy link

Collaborator

BrunoQuaresma commentedOct 1, 2025•
edited
Loading

The upgrade caused the following error:

node: ../deps/uv/src/unix/stream.c:456: uv__stream_destroy: Assertion `!uv__io_active(&stream->io_watcher, POLLIN | POLLOUT)' failed.

After downgradingmsw, a new error appeared only inWorkspacesPage.test.tsx:

<--- Last few GCs --->[2799:0x292c2000]    16790 ms: Scavenge 336.1 (443.3) -> 322.8 (443.3) MB, pooled: 32 MB, 6.45 / 0.00 ms  (average mu = 0.997, current mu = 0.996) allocation failure; [2799:0x292c2000]    16883 ms: Scavenge 336.7 (443.3) -> 326.8 (443.3) MB, pooled: 32 MB, 8.29 / 0.00 ms  (average mu = 0.997, current mu = 0.996) allocation failure; [2799:0x292c2000]    16989 ms: Scavenge 339.6 (443.3) -> 329.1 (443.3) MB, pooled: 32 MB, 9.87 / 0.00 ms  (average mu = 0.997, current mu = 0.996) allocation failure;

After some debugging, I traced it to@radix-ui/dialog. I didn’t find any open issues about memory leaks there, so my guess is it’s just using more memory than our default allocation. Jest has an option to increase the memory limit, but we should be fine for now.

Related issue:mswjs/msw#2537