thread 'vector-worker' panicked after set up the ALLOCATION_TRACING=true

[czd890]

A note for the community

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Problem

Set ALLOCATION_TRACING=true to investigate #23093. But the process crashed after a few hours.
logs:

thread 'vector-worker' panicked at src/internal_telemetry/allocations/mod.rs:111:13:
index out of bounds: the len is 128 but the index is 255
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
{
    "timestamp": "2025-05-28T10:11:11.169059Z",
    "level": "ERROR",
    "message": "An error occurred that Vector couldn't handle: the task panicked and was aborted.",
    "target": "vector::topology",
    "span": {
        "component_id": "internal_metrics_source",
        "component_kind": "source",
        "component_type": "internal_metrics",
        "name": "source"
    },
    "spans": [
        {
            "component_id": "internal_metrics_source",
            "component_kind": "source",
            "component_type": "internal_metrics",
            "name": "source"
        }
    ]
}
{
    "timestamp": "2025-05-28T10:11:11.169209Z",
    "level": "INFO",
    "message": "Vector has stopped.",
    "target": "vector"
}

Configuration

Version

{ "timestamp": "2025-05-28T07:56:26.166623Z", "level": "INFO", "message": "Vector has started.", "debug": "false", "version": "0.44.0", "arch": "x86_64", "revision": "3cdc7c3 2025-01-13 21:26:04.735691656", "target": "vector" }

Debug Output

Example Data

No response

Additional Context

No response

References

No response