1.0.3: Odd console spam

  • This section is closed. Please do bug reports over at the FTB GitHub repos.
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Trisscar

New Member
Jul 29, 2019
974
0
0
Version:
1.0.3

What is the bug:
So I loaded up the pack a moment ago, and everything worked fine till I loaded my current world. Once it started showing the blocks and such as opposed to the black space that comes before, this started spamming into my console (warning, it is long and repetitive, this section is from about five seconds of time);

http://pastebin.com/HceXx0Qk

I randomly decided to try lowering all of my video settings to see if that would affect it, and lowering my render distance from 7 to 6 somehow did.
I then proceeded to move to see if loading other chunks caused the issue, and it did. By loading chunks that, as far as I know, have nothing at all special in them. Some jungle and ocean biome and that's it, I haven't done anything there.
Any ideas what's causing this? it's currently not making me lag as far as I can tell, but the spam is worrying, since It wasn't doing this last time I played.

Mod & Version:


Paste.feed-the-beast.com log:


Can it be repeated:


Known Fix:
 
Huh, interesting. Well that kinda sucks, I was using it as my map program. XD Thank you though.
 
This is one of more readable Exceptions ...
Code:
java.lang.IndexOutOfBoundsException
 at java.io.RandomAccessFile.readBytes0(Native Method)
 at java.io.RandomAccessFile.readBytes(Unknown Source)
 at java.io.RandomAccessFile.read(Unknown Source)
 at javax.imageio.stream.FileImageInputStream.read(Unknown Source)
 at com.sun.imageio.plugins.common.SubImageInputStream.read(Unknown Source)
 at com.sun.imageio.plugins.common.InputStreamAdapter.read(Unknown Source)
 at java.io.SequenceInputStream.read(Unknown Source)
 at java.io.SequenceInputStream.read(Unknown Source)
 at java.util.zip.InflaterInputStream.fill(Unknown Source)
 at java.util.zip.InflaterInputStream.read(Unknown Source)
 at java.io.BufferedInputStream.fill(Unknown Source)
 at java.io.BufferedInputStream.read1(Unknown Source)
 at java.io.BufferedInputStream.read(Unknown Source)
 at java.io.DataInputStream.readFully(Unknown Source)
 at com.sun.imageio.plugins.png.PNGImageReader.decodePass(Unknown Source)
 at com.sun.imageio.plugins.png.PNGImageReader.decodeImage(Unknown Source)
 at com.sun.imageio.plugins.png.PNGImageReader.readImage(Unknown Source)
 at com.sun.imageio.plugins.png.PNGImageReader.read(Unknown Source)
 at javax.imageio.ImageIO.read(Unknown Source)
 at javax.imageio.ImageIO.read(Unknown Source)
 at mapwriter.region.SurfacePixels.loadImage(SurfacePixels.java:141)
 at mapwriter.region.SurfacePixels.load(SurfacePixels.java:46)
 at mapwriter.region.SurfacePixels.getPixels(SurfacePixels.java:65)
 at mapwriter.region.SurfacePixels.getOrAllocatePixels(SurfacePixels.java:71)
 at mapwriter.region.SurfacePixels.updateScaled(SurfacePixels.java:115)
 at mapwriter.region.Region.updateNextZoomLevel(Region.java:143)
 at mapwriter.region.Region.updateZoomLevels(Region.java:155)
 at mapwriter.region.SurfacePixels.updateChunk(SurfacePixels.java:91)
 at mapwriter.region.Region.updateChunk(Region.java:166)
 at mapwriter.region.RegionManager.updateChunk(RegionManager.java:123)
 at mapwriter.tasks.UpdateSurfaceChunksTask.run(UpdateSurfaceChunksTask.java:24)
 at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
 at java.util.concurrent.FutureTask.run(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)
For a Java-Dev its clear : there is something wrong with the image-files the map tries to read from your hard-drive. Either they are corrupted (maybe by the map itself while writing) or just missing (file of length 0).
Hard but short : dont use mapwriter as there is a serious problem with it.
 
But... the suspect chunks looked just fine on the map. So how many times a minute does the mapwriter try to update, assuming that's why it was returning this stuff? So silly. XD