pctx_executor 0.2.2

TypeScript execution environment orchestration
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

//! Stress test for concurrent V8 isolate usage.
//!
//! Deliberately does NOT use #[serial] — the goal is to reproduce the
//! V8 vector-out-of-bounds crash that occurs when type_check and
//! execute_code create JsRuntimes on different OS threads simultaneously.

use crate::{ExecuteOptions, execute};

#[test]
fn test_concurrent_execute_stress() {
    // Mirror the production pattern: multiple OS threads each with their own
    // single-threaded tokio runtime, calling execute() (type_check + execute_code)
    // concurrently. This creates overlapping V8 isolates without serialization.
    let handles: Vec<_> = (0..4)
        .map(|i| {
            std::thread::spawn(move || {
                let rt = tokio::runtime::Builder::new_current_thread()
                    .enable_all()
                    .build()
                    .unwrap();
                rt.block_on(async {
                    for j in 0..3 {
                        let code =
                            format!("const x{i}_{j}: number = {i} + {j}; export default x{i}_{j};");
                        let result = execute(&code, ExecuteOptions::new()).await.unwrap();
                        assert!(
                            result.success,
                            "iteration {i}_{j} failed: {:?}",
                            result.diagnostics
                        );
                    }
                })
            })
        })
        .collect();

    for h in handles {
        h.join().unwrap();
    }
}