Adding upstream version 115.7.0esr.upstream/115.7.0esr

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 24 insertions, 0 deletions

diff --git a/js/src/jit-test/tests/debug/Memory-allocationsLogOverflowed-01.js b/js/src/jit-test/tests/debug/Memory-allocationsLogOverflowed-01.js
new file mode 100644
index 0000000000..5e7176db34
--- /dev/null
+++ b/js/src/jit-test/tests/debug/Memory-allocationsLogOverflowed-01.js
@@ -0,0 +1,24 @@
+// Test basic usage of `Debugger.Memory.prototype.allocationsLogOverflowed`.
+
+const root = newGlobal({newCompartment: true});
+const dbg = new Debugger(root);
+dbg.memory.trackingAllocationSites = true;
+dbg.memory.maxAllocationsLogLength = 1;
+
+root.eval("(" + function immediate() {
+  // Allocate more than the max log length.
+  this.objs = [{}, {}, {}, {}];
+} + "());");
+
+// The log should have overflowed.
+assertEq(dbg.memory.allocationsLogOverflowed, true);
+
+// Once drained, the flag should be reset.
+const allocs = dbg.memory.drainAllocationsLog();
+assertEq(dbg.memory.allocationsLogOverflowed, false);
+
+// If we keep allocations under the max log length, then we shouldn't have
+// overflowed.
+dbg.memory.maxAllocationsLogLength = 10000;
+root.eval("this.objs = [{}, {}, {}, {}];");
+assertEq(dbg.memory.allocationsLogOverflowed, false);