From 36d22d82aa202bb199967e9512281e9a53db42c9 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 21:33:14 +0200 Subject: Adding upstream version 115.7.0esr. Signed-off-by: Daniel Baumann --- js/src/jit-test/tests/debug/job-queue-04.js | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 js/src/jit-test/tests/debug/job-queue-04.js (limited to 'js/src/jit-test/tests/debug/job-queue-04.js') diff --git a/js/src/jit-test/tests/debug/job-queue-04.js b/js/src/jit-test/tests/debug/job-queue-04.js new file mode 100644 index 0000000000..76cf241e8d --- /dev/null +++ b/js/src/jit-test/tests/debug/job-queue-04.js @@ -0,0 +1,24 @@ +// |jit-test| skip-if: !('oomTest' in this) +// Bug 1527862: Don't assert that the Debugger drained its job queue unless we +// actually saved the debuggee's queue. + +// Put a job in the queue. +Promise.resolve(42).then(() => {}); + +var g = newGlobal({ newCompartment: true }); +var dbg = new Debugger(g); +dbg.onNewScript = script => {}; + +// Cause an OOM while initializing the AutoDebuggerJobQueueInterruption, so that +// the destructor is run on an uninitialized instance. +// +// A properly initialized AutoDebuggerJobQueueInterruption asserts that the +// debugger left its job queue entry, before restoring the debuggee's job queue +// that it saved when it was initialized. But if OOM interrupts initialization, +// the job queue left on the JSContext is still the debuggee's, which we have no +// reason to expect is empty, so we shouldn't make any assertions about its +// state. The assertion must be conditional on proper initialization (and use +// the correct condition). +oomTest(() => { + g.eval("(function() {})"); +}, {expectExceptionOnFailure: false}); -- cgit v1.2.3