"Java SE Binary not responding" error

[rickarad]

I'm pretty sure this is a problem with my computer and not a bug in the game but any help would be welcome.  I can launch the log-in screen and get as far as starting a new game.  When the screen goes black and where there is typically the word "loading" in the top left corner, the game freezes.  When I use the task manager to stop the application, it says "Java SE Binary not responding". 

I've reinstalled Java multiple times, even a couple older versions but no luck.  I'm running Vista.

[Peter]

So the game window dispalys "Loading ..." but does never continue and does not show any error message? For how long did you wait? Could you please start the game so it enters the loading screen, wait for 3 minutes and then make a new post here where you attach your log.txt file. It is located in the mule/data directory.
Thanks.

[rickarad]

I've attached the log.txt file here.

Small detail - the screen never says "Loading...". It turns black and freezes.  I did get this to work properly on my office computer which is why I know the black screen actually says "loading..."

When I "end task" through the Vista task manager I get the error message,"Java(TM) Platform SE Binary not responding" error.  Any help would be great!

Appreciate it,

[bbrucker2]

I seem to be having the same error, has anything been discovered about this? I'm running Vista and installed the latest version of Java and checked for updated video drivers. Whenever I try to launch or join a game, it all freezes up.

[Peter]

Do you see your name pop up in the user list beside the chat where it says "Players" and "Visitors"? I see nothing wrong in your log. Have you tried clicking the black window and then pressing F5 to toggle to fullscreen mode?

[bbrucker2]

F5 seems to do nothing. Once I start or join a game, I just get a black screen, and it's all over. Last time, it crashed my computer, actually.

[bbrucker2]

Hey, how much memory is this thing supposed to use while running? Task Manager tells me it's taking up quite an impressive chunk of resources while it's not running.