[SERVER-72722] Throwing large objects kills MozJS thread without stack trace Created: 11/Jan/23  Updated: 29/Oct/23  Resolved: 02/Feb/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0-rc0

Type: Bug Priority: Major - P3
Reporter: Romans Kasperovics Assignee: Romans Kasperovics
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Execution
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: QE 2023-02-06
Participants:

 Description   

Throwing (and not catching) large errors in tests kills MozJS thread without printing the stack trace and the error message. This can happen when a JavaScript test assert fails and the message is over 64MB. The error message printed in the test log looks as follows:

[js_test:change_stream_pit_pre_images] exception: BufBuilder attempted to grow() to 377558926 bytes, past the 64MB limit.
[js_test:change_stream_pit_pre_images] exiting with code 1 

A developer is then left to wonder which test line has caused this.



 Comments   
Comment by Githook User [ 02/Feb/23 ]

Author:

{'name': 'Romans Kasperovics', 'email': 'romans.kasperovics@mongodb.com', 'username': 'romanskas'}

Message: SERVER-72722 Truncate long uncaught JavaScript error messages to 10KB
Branch: master
https://github.com/mongodb/mongo/commit/9bdd17de7c41ba7cdf7ec330b911d1a141e46d94

Generated at Thu Feb 08 06:22:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.