-
Notifications
You must be signed in to change notification settings - Fork 280
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
Extremely high memory usage #222
Comments
@johannesjo would you mind attaching a snippet or unit test that would reproduce this issue so we could profile it. |
This line could be the culprit of high memory usage: stacktrace.js/dist/stacktrace.js Line 2527 in c12fccd
A big source file will be splitted each time a function name must be found. |
we have had browser crashes recently when using the stack trace grabbing functionality - as well as performance issues when gathering stack traces. |
Would you mind submitting a pr with a fix, perhaps info could be cached. |
i noticed that my .map file was 111megabytes, by reworking my webpack.config i was able to get it down to 1mb and i think that is helping reduce the amount of crashing thats going on. to those in this boat, see if you can split your bundles to be smaller https://medium.com/hackernoon/the-100-correct-way-to-split-your-chunks-with-webpack-f8a9df5b7758 |
For a larger codebase with framework code (angular) I am using this module. When several errors are thrown and several stracktraces are requested in a short succession memory usage spikes absolutely out of control.
Expected Behavior
Should require a little bit less memory per error.
Current Behavior
Memory spikes out of control.
This is how stacktraces are requested.
The text was updated successfully, but these errors were encountered: