10-24-2017 04:30
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-24-2017 04:30
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
If I add an image to my resources folder, I get this error:-
- Internal error during build. Guru meditation: RangeError: Offset is outside the bounds of the DataView
It doesn't matter if I actually use the image or not.
The image was initially full screen (348x250) when it first failed, so I tried making it half sized but it still gives the same error.
If I delete the image from the resources folder it's fine.
Answered! Go to the Best Answer.

Accepted Solutions
10-26-2017 03:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-26-2017 03:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I had the same issue no matter how I saved it.
However... I saved it out as a JPG then opened it again and saved it as PNG and this time it worked.
All I can guess is it's a corrupt PNG somehow and resaving it does it.

10-24-2017 20:47
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-24-2017 20:47
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
What's the CSS values of X & Y?
If it goes outside the display currently it will give an error. This is fixed in the next firmware.

10-25-2017 00:02
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-25-2017 00:02
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
When I first added it I put it in at (0,0). It is a full screen sized image (348x250).

10-25-2017 02:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-25-2017 02:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-25-2017 16:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-25-2017 16:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Try loading into Paint dotNet or Pinta and re-saving the png and add it again.

10-26-2017 03:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-26-2017 03:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I saved it back out with Irfanview, with a different name, and it gives the same error.
Here's the image:-
https://drive.google.com/open?id=0B_STb3d-9OdPM3QwNWdjbUp5aEk

10-26-2017 03:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-26-2017 03:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I had the same issue no matter how I saved it.
However... I saved it out as a JPG then opened it again and saved it as PNG and this time it worked.
All I can guess is it's a corrupt PNG somehow and resaving it does it.

10-26-2017 04:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-26-2017 04:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
That worked! It did cross my mind to try saving as a different format but stupidly I never actually did it.
Thanks!
10-26-2017 06:49
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-26-2017 06:49
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Side note... I was using Photoshop and opened an image that was in grey mode and when I saved as png and ran app I just go a blank screen... I hadn't verified, but think images have to be RGB.

10-26-2017 07:00
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-26-2017 07:00
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
My image was definitely in RGB mode, no idea why it was dodgy (saved from GIMP, the original source was a JPG so it had already changed format).

01-05-2018 08:27
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

01-05-2018 08:27
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
I think the issue is actually due to interlacing. I took some images from the example projects that I knew worked and compared them to images that were causing build errors using `pngcheck` and I noticed that all of the working images were non-interlaced. I used ImageMagick to convert the images I was having issues with to non-interlaced and no more build errors. Hope this helps.
convert -interlace none interlaced.png uninterlaced.png
