Crash Report (client-side multiplayer)

Does this happen on the 1.4.3 pre-release?

This just occurred to me on a 1.4.2 server. I will check if it occurs on the newest pre-release under the same conditions.

I had no problem connecting to my home network server with the Minecraft_Server.jar from mojang.com for the current release 1.4.3 pre-release.

Duplicate of [MC-984]

Kumasasa, I'm not so sure it is a duplicate of that because I just checked an error log with someone on that page with the same issue, and it is slightly different from mine. Maybe this difference is based on operating system?

There was a user from MC-984 has a mac that expected this, and I have a pc.

Someone expecting errors similar to MC-984 Error log (http://bit.ly/YDSaLG)
-----------------
java.lang.ArrayIndexOutOfBoundsException: 0
at agl.a(SourceFile:239)
at awr.a(SourceFile:917)
at cr.a(SourceFile:41)
at bx.b(SourceFile:341)
at awr.d(SourceFile:98)
at awu.c(SourceFile:69)
at net.minecraft.client.Minecraft.l(SourceFile:1080)
at net.minecraft.client.Minecraft.J(SourceFile:582)
at net.minecraft.client.Minecraft.run(SourceFile:534)
at java.lang.Thread.run(Thread.java:680)

--------------------------------------------
My Error log

java.lang.ArrayIndexOutOfBoundsException: 0
at agl.a(SourceFile:239)
at awr.a(SourceFile:917)
at cr.a(SourceFile:41)
at bx.b(SourceFile:341)
at awr.d(SourceFile:98)
at awz.b(SourceFile:61)
at net.minecraft.client.Minecraft.l(SourceFile:1282)
at net.minecraft.client.Minecraft.J(SourceFile:582)
at net.minecraft.client.Minecraft.run(SourceFile:534)
at java.lang.Thread.run(Unknown Source)

The operating system should not matter, since both systems are running a Java VM.
Normally the call trace should be read backwards and since the first five calls are line-number-wise identical, I strongly suppose the same issue.

Agreed.