Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Rsbuild appears to have a memory leak after multiple rebuilds #8499

Open
shiqimei opened this issue Nov 16, 2024 · 6 comments
Open

[Bug]: Rsbuild appears to have a memory leak after multiple rebuilds #8499

shiqimei opened this issue Nov 16, 2024 · 6 comments
Assignees

Comments

@shiqimei
Copy link

shiqimei commented Nov 16, 2024

Version

System:
    OS: Linux 6.8 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
    CPU: (4) arm64 unknown
    Memory: 29.03 GB / 30.76 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh

Details

Image

Reproduce link

noop

Reproduce Steps

  1. run pnpm dev
  2. start development server for days, and then we will find the memory used by rsbuild get accumulated
@maxyasoon
Copy link

For me the memory usage also increased massively since 1.0.17. Maybe it is related.

@9aoy 9aoy self-assigned this Nov 19, 2024
@9aoy 9aoy transferred this issue from web-infra-dev/rsbuild Nov 21, 2024
@9aoy 9aoy removed their assignment Nov 21, 2024
@alessandro308
Copy link

We experience it on MacOS M1 too.

@ziggi
Copy link

ziggi commented Dec 17, 2024

Same on Windows, +500 MiB in memory after every file save.

Image

@ziggi
Copy link

ziggi commented Dec 17, 2024

It looks like this started with version 1.1.5.

Copy link

stale bot commented Feb 17, 2025

This issue has been automatically marked as stale because it has not had recent activity. If this issue is still affecting you, please leave any comment (for example, "bump"). We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

@stale stale bot added the stale label Feb 17, 2025
@luzfcb
Copy link

luzfcb commented Feb 17, 2025

It's the same issue reported on #8976

@stale stale bot removed the stale label Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants