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

Running basic express app with TSX causes high memory usage #689

Closed
4 of 6 tasks
joshk132 opened this issue Jan 11, 2025 · 2 comments
Closed
4 of 6 tasks

Running basic express app with TSX causes high memory usage #689

joshk132 opened this issue Jan 11, 2025 · 2 comments
Labels
bug Something isn't working pending triage

Comments

@joshk132
Copy link

Acknowledgements

  • I read the documentation and searched existing issues to avoid duplicates
  • I understand this is a bug tracker and anything other than a proven bug will be closed
  • I understand this is a free project and relies on community contributions
  • I read and understood the Contribution guide

Minimal reproduction URL

https://github.com/joshk132/bug

Problem & expected behavior (under 200 words)

When running the command tsx server.ts it results in the node process taking up more and more memory until it crashes. During this time the thread count also goes up.

OS: macOS Sequoia 15.2
Hardware: MacBook Air M1 16GB ram 256GB SSD.

I am not sure how to reproduce this error in GHA or get it to show in StackBlitz so adding this comment here.

Bugs are expected to be fixed by those affected by it

  • I'm interested in working on this issue

Compensating engineering work will speed up resolution and support the project

  • I'm willing to offer $10 for financial support
@joshk132 joshk132 added bug Something isn't working pending triage labels Jan 11, 2025
@privatenumber
Copy link
Owner

Thanks for filing!

Your reproduction doesn't currently demonstrate any problems, and feels more like a "help request" as it requires further investigation from others to confirm your claim.

To back up your claim, please:

  1. Use Node.js process.memoryUsage() to measure memory increase

  2. Confirm if this behavior is unique to tsx by comparing results against plain Node.js

  3. Use GitHub Actions to log and compare these results

Looking forward to your findings!

@privatenumber
Copy link
Owner

Closing in favor of #693

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working pending triage
Projects
None yet
Development

No branches or pull requests

2 participants