#tracing #allocator #alloc #global-allocator

wasm-tracing-allocator

A global allocator for Wasm that traces allocations and deallocations for debugging purposes

2 releases

0.1.1 May 10, 2019
0.1.0 May 10, 2019

#1385 in WebAssembly

Download history 11/week @ 2023-10-26 29/week @ 2023-11-02 9/week @ 2023-11-09 16/week @ 2023-11-16 10/week @ 2023-11-23 9/week @ 2023-11-30 22/week @ 2023-12-07 16/week @ 2023-12-14 9/week @ 2023-12-21 9/week @ 2023-12-28 26/week @ 2024-01-04 6/week @ 2024-01-11 12/week @ 2024-01-18 15/week @ 2024-01-25 38/week @ 2024-02-01 23/week @ 2024-02-08

88 downloads per month

MIT/Apache

56KB
151 lines

wasm-tracing-allocator

A global allocator for Wasm that traces allocations and deallocations for debugging purposes.

Build Status

wasm-tracing-allocator enables you to better debug and analyze memory leaks and invalid frees in an environment where we don't have access to the conventional tools like Valgrind. The tracing hooks are safely implemented in JS, outside the Wasm module and its linear memory, to ensure that the tracing code doesn't perturb results.

Table of Contents

Enabling the Tracing Allocator

First, add wasm-tracing-allocator to your Cargo.toml's dependency list:

[dependencies]
wasm-tracing-allocator = "0.1.0"

Next, configure wasm_tracing_allocator::WasmTracingAllocator as the global allocator:

// src/lib.rs

use std::alloc::System;
use wasm_tracing_allocator::WasmTracingAllocator;

#[global_allocator]
static GLOBAL_ALLOCATOR: WasmTracingAllocator<System> = WasmTracingAllocator(System);

Finally, make the JS implementations of the tracing hooks are available for your Wasm module to import:

  • On the Web, add this script before your Wasm module is instantiated:

    <script src="https://unpkg.com/wasm-tracing-allocator@0.1.0/js/hooks.js"></script>
    
  • On Node.js, require the hooks before your Wasm module is instantiated:

    require("wasm-tracing-allocator");
    

Analyzing and Debugging

Use your developer tools console to invoke methods of the global WasmTracingAllocator object to get analyses about allocations and deallocations.

The output is typically rendered with console.table:

Example output

WasmTracingAllocator.dumpLiveAllocations

Dump a table of live allocations to the console.

WasmTracingAllocator.dumpLiveAllocations({
  keyLabel: String,
  valueLabel: String,
  getKey: Object => any,
  getValue: Object => Number,
});
  • keyLabel: Optional. The string label used to describe the keys column in the table.

  • valueLabel: Optional. The string label used to describe the values column in the table.

  • getKey: Optional. Function from an allocation entry object to anything. The table will group and aggregate entries by their keys. Defaults to the stack at the time of the allocation.

  • getValue: Optional. Function from an allocation entry object to a number. The values for all entries with the same key are summed. Defaults to the byte size of each allocation; a potential alternative would be to ignore the argument and return 1 to count the number of allocations instead.

WasmTracingAllocator.dumpInvalidFrees

Dump a table of invalid frees (double frees, frees of things that were never allocated, etc...) to the console.

WasmTracingAllocator.dumpInvalidFrees({
  keyLabel: String,
  valueLabel: String,
  getKey: Object => any,
  getValue: Object => Number,
});
  • keyLabel: Optional. The string label used to describe the keys column in the table.

  • valueLabel: Optional. The string label used to describe the values column in the table.

  • getKey: Optional. Function from an invalid free entry object to anything. The table will group and aggregate entries by their keys. Defaults to the stack at the time of the deallocation.

  • getValue: Optional. Function from an invalid free entry object to a number. The values for all entries with the same key are summed. Defaults to counting the number of invalid frees.

Dependencies

~0.7–1.4MB
~28K SLoC