Memory access out of bounds

[eamodio]

Originally from: microsoft/vscode-js-debug#185

Here is the source file and source map that caused the issue.
source.zip

[skirdey]

Hey folks, is this issue anywhere in the queue?

[markboyall]

I'm also seeing a similar issue.

 RuntimeError: memory access out of bounds
    at wasm-function[18]:1732
    at wasm-function[22]:493
    at wasm-function[25]:143
    at wasm-function[1]:405
    at wasm-function[34]:95
    at _wasm.withMappingCallback (D:\dev\epro\Epro.Mobile\node_modules\source-ma
p\lib\source-map-consumer.js:664:26)
    at Object.withMappingCallback (D:\dev\epro\Epro.Mobile\node_modules\source-m
ap\lib\wasm.js:95:11)
    at BasicSourceMapConsumer.generatedPositionFor (D:\dev\epro\Epro.Mobile\node
_modules\source-map\lib\source-map-consumer.js:663:16)

[steinybot]

I'm getting this too:

RangeError: Start offset -1357356032 is outside the bounds of the buffer
  at new Uint8Array@<anonymous>(Unknown Source)
  at BasicSourceMapConsumer._parseMappings(https://localhost:8080/erp-front-fastopt-bundle.js:436315:25)
  at BasicSourceMapConsumer._getMappingsPtr(https://localhost:8080/erp-front-fastopt-bundle.js:436300:12)
  at {anonymous}()(https://localhost:8080/erp-front-fastopt-bundle.js:436495:14)
  at Object.withMappingCallback(https://localhost:8080/erp-front-fastopt-bundle.js:438741:11)
  at BasicSourceMapConsumer.originalPositionFor(https://localhost:8080/erp-front-fastopt-bundle.js:436493:16)

[steinybot]

It turns out the issue in my case is that I was creating too many consumers without destroying them. The behaviour still seems a little fishy to me so I raised fitzgen/source-map-mappings#19.

[xiaobai2017666]

It turns out the issue in my case is that I was creating too many consumers without destroying them. The behaviour still seems a little fishy to me so I raised fitzgen/source-map-mappings#19.

You need to call consumer.destroy () after each SourceMapConsumer to release the memory occupied by new sourceMap.SourceMapConsumer.

Here is an example.

async function getSourceMessage({
    col = 0,
    row = 0,
    file,
}) {
    const DATA = file.toString();
    const consumer = await new sourceMap.SourceMapConsumer(DATA);
    const po = consumer.originalPositionFor({line: row, column: col });
    consumer.destroy();

    return po;
}

[markboyall]

You can get this error even when using the withConsumer function, probably occurs when the source map is simply very large.

[kirill578]

consumer.destroy() does not seem to be related in my case. I am unable to reproduce it locally, but it seems to be consistent when running on an AWS lambda with a 5 MB source map.

[kirill578]

Downgrading to version 5.6 resolved the issue

[nornagon]

I'm seeing this issue sporadically on 0.7.4 when running with many SourceMapConsumers open at once. Both the RangeError and the memory access out of bounds.