Planet M.U.L.E.
Planet Mule 1 => Bugs 1.3.x => Topic started by: Gohar on February 16, 2011, 00:46
Title: Unusual bug - Planet Mule forced closed Post by: Gohar on February 16, 2011, 00:46 Hi PM universe,
I played a game today called "SapperRE (29.79) hosted by Aufklarer. In round 11, both myself and another user (mary) had an error message come up and then entire programme on my laptop closed. This was simultaneous for both me and Mary. The 3rd guest was unaffected. The error message was something along the lines of: "Null point error anulled" I'm not sure about the annulled word, maybe thats an artifact in my memory, I never got this message before. It certainly isnt a internet connection problem as far as i can tell. Would be very interested to know if this problem has occurred before, Title: Re: Unusual bug - Planet Mule forced closed Post by: Spoonwood on February 16, 2011, 00:50 I once had the program close on me, but I don't know if I had that same message.
Title: Re: Unusual bug - Planet Mule forced closed Post by: Aufklarer on February 16, 2011, 00:55 I can confirm the above to be true.
As the host of the game, in round 11 Gohar and Mary both disconnected from the game (unintentionally) at the beginning of the auction round, if my memory serves correctly it was smithore auction?. Both disconnections happened instantly with no prior lag or warning of latency issues. The plot selections were a little slow but otherwise latency wasnt too bad prior to this happening. Game: http://www.planetmule.com/hi-score-game/game?game_id=39653 Game chat: http://www.planetmule.com/server/chats/chat_game_39653_user_19555.html AI instantly assumed the places of the DC'd players, Spoonwood and I were unaffected. Title: Re: Unusual bug - Planet Mule forced closed Post by: Null on February 16, 2011, 01:09 "Null point error anulled"
I didnt do it!!!! :P Title: Re: Unusual bug - Planet Mule forced closed Post by: Peter on February 28, 2011, 14:01 Thanks for the report. Your log shows the exact error and it's a fault in the code that caused it. I've noted to fix it for the next release. The error message you got was "Null Pointer Exception" in case anyone wondered.
|