BLXBenchBLXBench UI
blxbench

Benchmark

Misc

DocsOur TestsPassSponsor / Partnership
DocsOur TestsPassSponsor / Partnership
BLXBenchBLXBench UI
blxbench

Benchmark

Suite

Misc

DocsOur TestsPassSponsor / Partnership
DocsOur TestsPassSponsor / Partnership
  1. Home
  2. Our Tests
  3. Reason-Rc-Memory-Leak-Closure
blxbench

Test fixture

Reason-Rc-Memory-Leak-Closure

Reasoningv2 — Resiliencemediumscorer: rubric_json_metrics

Arithmetic, symbolic steps, and structured problem solving.

How it is scored

The model receives the prompt (and optional system message). The run uses scorer rubric_json_metrics with the JSON configuration below. Pass/fail and partial credit are determined entirely by that scorer against the model output; no human grading.

User prompt
Return JSON only with keys answer, evidence, constraints. A module creates a large array and captures it in a closure. The closure is returned as a callback and stored in a global registry. The array is never released. Memory usage grows over time. What is the root cause of the memory leak?
Scorer config
{
  "metrics": {
    "accuracy": {
      "checks": [
        {
          "contains": [
            "closure"
          ]
        },
        {
          "contains": [
            "memory leak"
          ]
        },
        {
          "contains": [
            "global registry"
          ]
        }
      ]
    },
    "evidence": {
      "checks": [
        {
          "contains": [
            "large array"
          ]
        },
        {
          "contains": [
            "never released"
          ]
        },
        {
          "contains": [
            "captured"
          ]
        }
      ]
    },
    "constraint": {
      "checks": [
        {
          "contains": [
            "garbage collection"
          ]
        },
        {
          "contains": [
            "strong reference"
          ]
        },
        {
          "contains": [
            "deregister"
          ]
        }
      ]
    }
  }
}
Run parameters

temperature

0

max_tokens

500

timeout (s)

120

type

scored

file

reason-rc-memory-leak-closure.json

← PreviousReason-Rc-Login-Timeout
|
Next →Reason-Rc-Null-Pointer-Call

BLXBench

Community driven leaderboardPublic benchmark runner — run in your environment, share results with the community.

© 2026 BLXBench by bitslix.com

ProvenanceAggregated from user runs
Scope41 / 11 / 490
Latestrun_3d5451 / 459 / $1.75
TermsPrivacy