Program crash while chatting

[doktorbuzzo]

Rats.

Here's a game (still currently in progress as I report) that I just abandoned due to my P.M. program crashing as I typed chat text before my turn: http://www.planetmule.com/hi-score-game/game?game_id=41783. So very sorry, guys, I did not abandon, my sneaky computer done blowed up!

I think I've seen this before but I can't recall the game. It was recent, though, certainly when running the current P.M. version.

Here's a link to the Java crash report: http://bit.ly/i6QfQ2

Here's the text from my log_init file:

 INFO [Properties.<init>]                           VERSION: 1.3.4
  INFO [Properties.<init>]                           Classpath: data.jar
  INFO [Properties.<init>]                           Java VM: 19.1-b02-334
  INFO [Properties.<init>]                           Java Runtime: 1.6.0_24-b07-334-10M3326
  INFO [Properties.<init>]                           OS: Mac OS X 10.6.7 x86_64
  INFO [Properties.<init>]                           Java Library Path: lib
  INFO [Properties.<init>]                           Max Memory: 265093120
  INFO [Properties.<init>]                           Avaialble Processors: 2
  INFO [PropertiesBase.readFromFile]                 Reading Settings from file settings.txt
  INFO [SubstanceLoader.initLookAndFeel]             Window Skin: Default
  INFO [Main.main]                                   lpSolve: 5.5 Release 0 Build 15
  INFO [SoundPlayer.initialize]                      Initializing Sound System
  INFO [SlickLogSystem.info]                         Initialising sounds..
  INFO [SlickLogSystem.info]                         - Sound works
  INFO [SlickLogSystem.info]                         - 64 OpenAL source available
  INFO [SlickLogSystem.info]                         - Sounds source generated
  INFO [MasterClient.setServerAddress]               MasterClient: Address http://www.planetmule.com/server
  INFO [MasterClient.logSend]                        MasterClient: Sending Login
  INFO [MasterClient.apply]                          MasterClient: Session ID: 78983be3fb4289d2778df71e3c604244
  INFO [Login$MasterListener$1.run]                  Logged in as "doktorbuzzo" (id 17294)
  INFO [MetaFrame.<init>]                            Creating Meta Frame
  INFO [MapSkinParser.findSkins]                     No extra skins found
  INFO [MasterClient.logSend]                        MasterClient: Sending Enter Lobby
  INFO [Login.dispose]                               Disposing login
  INFO [Main.main]                                   Creating game container
  INFO [MuleGameContainer.<init>]                    LWJGL Version: 2.4.2
  INFO [MuleGameContainer.<init>]                    Desktop Display Mode: 1600 x 900 x 32 @0Hz
  INFO [MuleGameContainer.<init>]                    Current Display Mode: 1600 x 900 x 32 @0Hz
  INFO [MuleGameContainer.<init>]                    Display Adapter: null
  INFO [MuleGameContainer.<init>]                    Display Driver: null
  INFO [MuleGameContainer.setVSync]                  Setting vsync: true
  INFO [MuleGameContainer.<init>]                    Setting pixel format
  INFO [MuleGameContainer$1.run]                     Pixel format: Samples=0 Alpha=0 Depth=8 Stencil=0
  INFO [MuleGameContainer.<init>]                    GL Vendor: NVIDIA Corporation
  INFO [MuleGameContainer.<init>]                    GL Renderer: NVIDIA GeForce 320M OpenGL Engine
  INFO [MuleGameContainer.<init>]                    GL Version: 2.1 NVIDIA-1.6.26
  INFO [MuleGameContainer.<init>]                    GL Max Texture Size: null
  INFO [SlickLogSystem.info]                         Use Java PNG Loader = true
  INFO [MuleGameContainer.<init>]                    Display finished
  INFO [Main.main]                                   Entering game loop
 

I hope this helps track down & zap this nasty bug!

Thanks,

doktorbuzzo

P.S.: LOL yes, the text I was trying to type was indeed "uckfay."

[doktorbuzzo]

Sigh.

Here's another similar crash report http://bit.ly/geEgQE from game http://www.planetmule.com/hi-score-game/game?game_id=41922. As before, the program on my computer crashed while I attempted to enter chat text.

What a bummer!

doktorbuzzo

[doktorbuzzo]

Dammit! Again!

Game log: http://www.planetmule.com/hi-score-game/game?game_id=42008

Java crash log: http://bit.ly/gecwhJ

Please somebody have a look at this, it's the third time in a week that this crash behavior has happened to me.

It is definitely related to keyboard input for chatting.

Every time this has occurred it was when I was getting chirpy. I like chirpy. I'm a Flapper fer cryin' out loud! Chirp is what I do!

Tweet tweet,

doktorbuzzo

[doktorbuzzo]

This is for @NilacTheGrim who asked about how one can post a crash log to the forum. The request for this info was initially misposted to a different bug thread.

Here's the info I provide and how I get it. I'm running Mac OS X as well.

1. The log_init.txt file has some information about things like the OS version, the Java version, system memory, graphics processor, etc. that help to explain the nature of the host computer. To retrieve log_init.txt, do the following:

• Open a Finder window.
• Go to the Applications folder (/Applications) or just press Shift-Command-A (??A), or go to the place where the mule application is installed on your system.
• You need to "Show Package Contents" for the mule application. Do this by either Control-clicking it and selecting "Show Package Contents" or you can use the "Action" menu button (the little gear-shaped icon near the center-top of the Finder window) to do so.
• The log files, including log_init.txt, are found in the "Contents > Resources > Java > data" folder (the Unix-style path is typically something like /Applications/mule.app/Contents/Resources/Java/data/log_init.txt ). You can copy the log_init.txt file to a different location if you want to upload it, or you can select & copy all of its contents to post them directly since it isn't a very large file.

2. The Mac OS X system will also generate a crash log every time a program crashes. You can find these handy text files (which typically are very large since they contain a lot of information) using the "Console" application, which is in your system's "Utilities" folder. To retrieve a crash report, do the following:

• Open a Finder window.
• Go to the Utilities folder (/Applications/Utilities) or just press Shift-Command-U (??U).
• Run the Console application.
• Crash reports are grouped into a category called "Diagnostic and Usage Information," which is one of the categories you'll see in the left panel of the Console app's main window.
• Crash reports from the Mac OS X mule application are generally named something like "java_2011-04-01_233539_zzzz.crash" since the mule app is a Java program. The rest of the filename is three strings that you can see will resemble a date ("2011-04-01"), a time ("233539," for 11:35:39 P.M. my local time) and the name of your computer ("zzzz" in my case).
• Locate the relevant crash report based on the time at which your mule program crashed. There may be a lot of crash reports to choose from but usually you can narrow things down by restricting your search to those starting with "java" and then looking at the date & time parts of the log file names.
• Once you've found your crash report, select it from the list on the left to see all of its text appear in the right side of the Console app's main window.
• To copy this text, you can just click your mouse in the text area and press Command-A (?A) to select all of the text. Then press Command-C (?C) to copy the text.
• Open any text editor, like "TextEdit."
• Click inside the editor's text area and press Command-V (?V) to paste the crash log file's contents. Save the file.
• The crash log will be too long to post to the Planet M.U.L.E. forum. What I'm able to do is to upload the saved copy of the log to one of my webpages I get for free from my ISP. You'll have to do something similar, or upload it to a filesharing service that others can read from. Once you've uploaded the file to the 'net, copy the link to it and paste that link into your bug report when you post to the forum.

Hope this helps,

doktorbuzzo

[Peter]

Thanks for the detailed reports. I've noted that we should look into this for the next release.