Not too sure what went wrong, other than that I mounted the horse (saddled) and opened my inventory at almost the same time. The client crashed and died instantaneously (no error screen) but didn't stop the 'Java.exe' process, which retained it's memory (the process had to be closed manually, else the launcher refused to start a new client due to the process already being in use).
When I attempted to go back into the world, after the loading screen (after 'Downloading World' prompt), it instantly crashed, exiting completely out of the client without an error screen, and the Java.exe process was still running again.
This output from the launcher may be relevant to the issue, as it seems to recall some information from the moment of the crash;
Client> 2013-04-20 01:14:10 [SERVER] [INFO] Preparing start region for level 0
Client> 2013-04-20 01:14:11 [SERVER] [INFO] Preparing spawn area: 99%
Client> loading single player
Client> 2013-04-20 01:14:11 [SERVER] [INFO] sebbeshs[/127.0.0.1:0] logged in with entity id 248 at (385.92508199461025, 66.7000000178814, -238.48337619840805)
Client> java.io.FileNotFoundException: http://assets.minecraft.net/1_6_has_been_released.flag
Client> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
Client> at kq.a(SourceFile:237)
Client> at bhq.run(SourceFile:114)
Client> at java.lang.Thread.run(Unknown Source)
Client> 2013-04-20 01:14:12 [SERVER] [INFO] Saving and pausing game...
Client> 2013-04-20 01:14:12 [SERVER] [INFO] Saving chunks for level '[13w16a] ADVENTURE!!!'/Overworld
Client> u: Ticking screen
Client> at asm.j(SourceFile:1101)
Client> at asm.N(SourceFile:566)
Client> at asm.c(SourceFile:522)
Client> at net.minecraft.client.main.Main.main(SourceFile:78)
Client> Caused by: java.lang.ArrayIndexOutOfBoundsException: -97
Client> at org.lwjgl.input.Keyboard.getKeyName(Keyboard.java:429)
Client> at bas.a(SourceFile:624)
Client> at fa.a(SourceFile:45)
Client> at cj.b(SourceFile:64)
Client> at bas.d(SourceFile:92)
Client> at bbf.c(SourceFile:31)
Client> at asm.j(SourceFile:1091)
Client> ... 3 more
Client> b@190a0d51
Client> 2013-04-20 01:14:13 [CLIENT] [INFO] Stopping!
Client> 2013-04-20 01:14:13 [SERVER] [INFO] Saving chunks for level '[13w16a] ADVENTURE!!!'/Nether
Client> 2013-04-20 01:14:13 [SERVER] [INFO] Saving chunks for level '[13w16a] ADVENTURE!!!'/The End
Client>
Client> SoundSystem shutting down...
Client> 2013-04-20 01:14:14 [SERVER] [INFO] Stopping server
Client> 2013-04-20 01:14:14 [SERVER] [INFO] Saving players
Client> removing player mount
Client> 2013-04-20 01:14:14 [SERVER] [INFO] Saving worlds
Client> 2013-04-20 01:14:14 [SERVER] [INFO] Saving chunks for level '[13w16a] ADVENTURE!!!'/Overworld
Client> 2013-04-20 01:14:14 [SERVER] [INFO] Saving chunks for level '[13w16a] ADVENTURE!!!'/Nether
Client> 2013-04-20 01:14:14 [SERVER] [INFO] Saving chunks for level '[13w16a] ADVENTURE!!!'/The End
Steps to reproduce:
1. Bind "sneak" to "button 2" (right-click).
2. Bind "use item" to anything else ("h" for example)
3. Place a boat with "h".
4. "h" to enter boat - crash
Related issues
is duplicated by
Attachments
Comments


I am having this issue, also. It happens when I mount a horse or get in a boat or minecart. I end up having to NBT edit my player.dat file and remove the "riding" group of tags, and then I'm able to connect again.
Huge bug, please fix!

Yup, huge bummer. One of the most user-visible changes in 1.6 is the addition of horses and the ability to ride them, but if you try to share the experience, the rider gets booted immediately from the server with the NPE.
Note this also happens if a user shares their single-player world over a LAN.
As Sean said, one workaround is to NBT to edit the player, and stop trying to ride horses for now 😞

dupe of MC-13628

Issue has been resolved as of 13w16b. I was able to log back into the "corrupt" world with no other obvious consequence than 2 duped horses.
Hooray for Mojang!

This issue has not been resolved for me in 13w18c.

my issue was resolved with this release.

If this isn't fixed for 1.6 when it comes out its gonna be a HUGE dissapontment for people that have there controls differently.

It is fixed in 1.6?
Fix Version/s: Minecraft 1.6

Nvm.. its fixed.

I looked at the Mojang site and it said it was fixed in yesterdays snapshot.