-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Ability to disable forced serialization of error.stack #1581
Comments
Previous issues: #1285 |
Are you talking about Promise.coroutine? |
No, it seems that bluebird might always be forcing serialization of error.stack - I'm not sure yet. I opened a jest issue too jestjs/jest#7879 |
Forced serialization is to avoid memory leak isn't it? |
Yes, but if there was a way to disable it for test environments, it would probably help. There regardless of whether the stack is actually needed if there is a promise error, it gets force-serialized which is really slow with source maps enabled and times out the first test. |
I see, could probably create a flag for lazy serialization? PR welcome |
Most versions since 2.x
All platforms
Bluebird forces serialization of error.stack. In test environments with source maps support (for example, jest) this causes test timeouts since bluebird will attempt to read the stack string, blocking the test up to a few seconds.
Test case to reproduce coming soon - in the mean time I wonder what precisely was the original reason that we forced this serialization.
The text was updated successfully, but these errors were encountered: