1.7.2 forge builds 1007 and 1019 ArrayIndexOutOfBoundsException

[zarb]

Hi,

 

I am encountering a crash. It only appears to happen in a specific place on my server, I can roam the server just fine, if I avoid this one special place. After some more debugging I have narrowed it down. The crash happens RIGHT as I try to walk into a chunk that contains my witch farm. I can tell this because when I rejoin the server w/o forge after the crash I am standing on that very chunk border. the farm features larger amounts of redstone blocks, tripwire, hopper pairs feeding into one another and a drop shaft (possibly lots of lighting updates?). I have since copied the server world and ran it in singleplayer... same crash. HOWEVER if I TNT my witch farm to pieces, the crash no longer occurs.

 

Please note, that I am not using ANY mods (only forge clientside), neither on the client nor server.

 

 

java.lang.ArrayIndexOutOfBoundsException

at java.lang.System.arraycopy(Native Method)

at net.minecraft.client.renderer.Tessellator.func_147565_a(Tessellator.java:205)

at net.minecraft.client.renderer.WorldRenderer.func_147889_b(WorldRenderer.java:280)

at net.minecraft.client.renderer.RenderGlobal.func_72719_a(RenderGlobal.java:718)

at net.minecraft.client.renderer.EntityRenderer.func_78471_a(EntityRenderer.java:1249)

at net.minecraft.client.renderer.EntityRenderer.func_78480_b(EntityRenderer.java:1060)

at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:979)

at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:869)

at net.minecraft.client.main.Main.main(SourceFile:103)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at net.minecraft.launchwrapper.Launch.launch(Launch.java:134)

at net.minecraft.launchwrapper.Launch.main(Launch.java:28)

 

 

 

[LexManos]

Interesting, this shouldnt be an issue on our end.

However, send me a copy of your world and a coord of what causes you to die.

[zarb]

I could whitelist you on the server and show you if thatd be easier for you too. Or I can pack up the map for you, no problem.

... Your call.

[LexManos]

There are reasons why I asked for what I asked for -.-

Its easier to debug locally  then remotely.

[zarb]

gotcha. PM is comin up in a bit

[zarb]

well actually it says message blocked (PMs disabled?)

 

Thing is, Id rather not post my world publically in a search engine indexed place, which is why Id prefer PMing

[LexManos]

So you store your social security number in your world?

That would be silly.

Just post it.

[zarb]

meh fine. just delete this post after you read it.. or edit out the link or something.

 

 

you can download the world from *bleep*

I should note that chrome browsers throw a tantrum with links like these because of the webserver port.

 

You can find the problematic area by teleporting to

 

/tp -2048 70 1346

Look south. If you head towards the sandstone bridge... one of the offending chunks starts exactly 1 block before the bridge starts.

Offending chunks are (to my knowledge): -129 to -126 , 85 to 87.

 

May I recommend night vision to be able to see better?

/effect LexManos 16 3600

 

PS: sorry it took so long, my DNS server went down right as I wanted to write this and as such couldnt login into minecraft and all that jazz.

[LexManos]

link doesnt work

[zarb]

thats weird. works fine for me. like I said, it doesnt work with chrome browsers because chrome has some retarded botnet protection or whatever it is

[zarb]

I actually managed to shrink the world download significantly by deleting all the regions that are irrelevant to this crash. I have also verified that the crash still occurs with a stripped world like that. Furthermore I have put it onto a different host: *bleep*

 

Also, for future reference, while verifying, that the crash still occurs, I got this

 

---- Minecraft Crash Report ----
// This is a token for 1 free hug. Redeem at your nearest Mojangsta: [~~HUG~~]

 

 

 

 

[LexManos]

Fixed

[zarb]

Much appreciated!

 

If this question is not out of line. I have noticed that in minecraft (vanilla as well as forge), having a larger hollowed out area (or roofed for that matter) without daylight is prone to tank the frame rates REALLY hard. I have previously seen this by hollowing out a 32x32x3 box just under groundlevel. And as soon as theres ANY kind of update in the area (such as block placement/removal or redstone) the FPS tanks really hard and the F3 display shows 100+ chunk updates. I would guess this to be lighting related.

 

First of all, am I right in the reasoning for the tanking? Secondly... is there an "easy" ingame fix one can employ to avoid this issue or at least lessen the impact this has on fps?

 

Im asking you this since you seem to have recently dug into the lighting while fixing this crash

[LexManos]

Different area of code, and no I havent experianced that before...

Howerver, I do many underground caverns, as thats how I like to play. I never get issues like that.

[zarb]

odd. but thanks anyway!