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.

[Packager] Offset is out of bounds

See original GitHub issue

Hey guys,

Ever since I upgraded to 0.4.2, I keep getting this error from time to time in the middle of development:

 ERROR  Offset is out of bounds
Error: Offset is out of bounds
    at Object.fs.read (evalmachine.<anonymous>:462:11)
    at Object.fs.read (/Users/josebalius/Sites/Ravedish/node_modules/react-native/node_modules/graceful-fs/polyfills.js:237:15)
    at /Users/josebalius/Sites/Ravedish/node_modules/react-native/node_modules/image-size/lib/index.js:46:8
    at OpenReq.Req.done (/Users/josebalius/Sites/Ravedish/node_modules/react-native/node_modules/graceful-fs/graceful-fs.js:141:5)
    at OpenReq.done (/Users/josebalius/Sites/Ravedish/node_modules/react-native/node_modules/graceful-fs/graceful-fs.js:61:22)
    at Object.oncomplete (evalmachine.<anonymous>:107:15)

Has any ran into this before? Not a big issue but it sucks to have to keep restarting the packager.

Issue Analytics

State:
Created 8 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

4reactions

weremaxcommented, Aug 11, 2016

I had this error this morning. Working thru the issue and posting this for anyone else that may get this: in my case this was an image that was empty the file existed and was named but had no content for the system to read. Once the image was fixed reran after closing the process window and everything back to normal.

0reactions

christopherdrocommented, Jun 30, 2015

👍