TL;DR

Implementing more granular timeout enforcement that can interrupt CPU-intensive operations mid-execution is likely to fix the resource exhaustion issue.

Guidance

• Review the isolated-vm-bridge.ts file to understand the current timeout enforcement mechanism and identify potential points for improvement.
• Consider adding operation counting or periodic yield checks to detect and interrupt long-running operations, such as regex catastrophic backtracking or large JSON.parse operations.
• Evaluate the feasibility of implementing async yield points in complex computational loops to allow for timeout enforcement.
• Assess the impact of increasing the memory limit or timeout duration on the overall performance and security of the system.

Example

No specific code example is provided, as the issue requires a more fundamental change to the timeout enforcement mechanism.

Notes

The recommended fix requires a thorough understanding of the isolated-vm-bridge.ts file and the underlying mechanics of the script.runSync method. The implementation of more granular timeout enforcement may have performance implications that need to be carefully evaluated.

Recommendation

Apply workaround: Implementing more granular timeout enforcement is a complex task that requires careful consideration of performance and security implications. A workaround, such as increasing the memory limit or timeout duration, may be necessary until a patched version is available. However, this may not fully address the underlying issue and should be carefully evaluated.