Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

RangeError: offset is not uint

See original GitHub issue

Hi there,

I’m loving music-metadata-browser. Nice work!

Every so often, though, when processing a file, it throws an error like the below for certain songs:

RangeError: offset is not uint
    at checkOffset (index.js:1165)
    at Uint8Array.readUInt32LE (index.js:1218)
    at ID3v24TagMapper.postMap (ID3v24TagMapper.js:173)
    at ID3v24TagMapper.mapGenericTag (GenericTagMapper.js:78)
    at CombinedTagMapper.mapTag (CombinedTagMapper.js:42)
    at MetadataCollector.toCommon (MetadataCollector.js:239)
    at MetadataCollector.addTag (MetadataCollector.js:102)
    at ID3v2Parser.addTag (ID3v2Parser.js:195)
    at ID3v2Parser.parseId3Data (ID3v2Parser.js:189)

When I say “certain songs” I mean mp3 files, and that the error is consistent, in that it will always happen for some files and it will never happen on others.

What are some things to look at with regards to the file to determine why a problematic file is causing the error?

I’ve read through issue #15 but couldn’t quite figure out how to troubleshoot the issue.

I dropped some of the files in question on the Audio Tag Analyzer, and compared those to “known good” files, but I’m not seeing thing that sticks out.

Any advice would be greatly appreciated.

P.S. I’m using "music-metadata-browser": "^1.1.1" in a create-react-app

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:31 (15 by maintainers)

github_iconTop GitHub Comments

Borewitcommented, Aug 9, 2019

Workaround released in music-metadata-browser v1.2.2.

Does this work for you guys, without the yarn buffer resolution?

kimfuciouscommented, Aug 10, 2019

Hi @Borewit , thanks for your continued efforts on this cool project.

I just removed node_modules, removed buffer from packages.json, removed yarn.lock, and bumped mm-b to v1.2.2, then did a clean npm install.

I also removed the shim bits in the app.

And… 🎉 !

Read more comments on GitHub >

github_iconTop Results From Across the Web

RangeError: offset is not uint · Issue #311 · tulios/kafkajs - GitHub
I am getting the error RangeError: offset is not uint from the example code. Any ideas? <script> export default { name: "KafkaClient", props:...
Read more >
Node.js FS - Offset is out of range, but also in range?
I'm attempting to read a file to memory using Node.js and receiving an out of range error for the offset though it falls...
Read more >
VOLTage Subsystem Introduction - Keysight RFMW Sitemap
Front panel: The offset value is clipped to the maximum value allowed that will not exceed the LIMit setting, and a "Data out...
Read more >
Debug and troubleshoot WebGL builds - Unity - Manual
The browser console log prints this error when the content tries to load an AssetBundle compressed using LZMA, which Unity WebGL doesn't support....
Read more >
Node.js v19.3.0 Documentation
Class: AssertionError; Class: RangeError; Class: ReferenceError ... value is coerced to a uint32 value if it is not a string, Buffer , or...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found