Sorry, was having a vacation.

No, it doesn't crash every 30 seconds, but returns to menu instead. Its way more annoying than just seeing the banner on top of the game.

I'm not running crash reporter.

@Mikko Actually the game doesn't crash after 30 seconds, just returns to the main menu. I noticed this because Crash Reporter doesn't report any crash when the game is pausing. It seems that the 30 seconds bug is the only way for the game to "properly" close itself without crashing... ;)

Why can't it normally close itself?

I don't deliberately make programs crash, I just hadn't noticed it.

I still haven't been able to reproduce crash at 30 seconds bug, which I believe is the problem as Tuomo is having.

Just tried, returns to menu every 30 secs even without Crash Reporter. Ok, if you have not Crash Reporter installed you can't actually notice that the game crashes everytime it closes a match, but they are still crashes. Why can't it normally close itself?

@Emanuele Please try running without the crash reporter and see if it still goes to menu every 30 seconds.

@Tuomo Are you also running crash reporter?

Techically game crashes when it ends but you don't notice it unless you are running crash reporter.

@Mikko - Yes, every 30 seconds it goes to the menu - After exiting from host mode (the searching for enemy window), Crash Reporter pops itself up saying battlegweled has just crashed, as said by Tuomo. The game "returns" to the menu - The client mode problem is probably my fault, sorry for that, but it would need better explanation.

@Emanuele When you say games pauses every 30 seconds, do you mean that it goes to menu screen?

How does it crash when exiting host mode? Crashes completely to desktop, no menu screen? Did you start multiplayer game before this (client connected and actual game started)?

How does it crash when starting client mode? did you enter hostname or ip address of the oppenent? It's true that it bails out immediately if there's no server running and that there's no error message displayed. Or it's not explained that you need two N900 to play multiplayer game.

This game is just unplayable, can't understand why it has so many thumbs up. When I play single player, It automatically pause the game every 30 seconds. It crashes when trying to start a game in Multiplayer Client Mode and it crashes when exiting the host mode. This just can't go to Extras, it's the most bugged and unstable app I've ever seen.

@Tuomo OK I see the game end crash, I think it happens in hgw_context_destroy function. Maybe the function (or the whole hgw library) is used wrong, but I didn't read the whole source code :) As such the crash is not visible to users, unless it is somehow related to your other problem.

"game is not yet started" bug (https://bugs.maemo.org/show_bug.cgi?id=3748) doesn't crash the game for me. The change which I made to hgw usage is in exiting the game not in starting.

Do you have hildon-games-wrapper0 version 1.9.4-3+0m5 and osso-games-startup version 1.6.40-1+0m5?

@Mikko: it SIGABRTs, dies instead of exiting cleanly. You basically don't see the difference normally, since the game process ends anyways and you return to game launcher process. Try attaching a debugger to the process and you'll see. Its not really visible to end user, but crasher anyways.

The "game is not yet started" behaviour changed from 0.9-4, and changelog states you had some changes, but it just made it worse.

@Tuomo, which firmware version you are using?

What do you mean with aborts when you lose? It's supposed to return to menu screen after each game (ie. it's not a bug).

In this version, when "game is not yet started" bug happens, the game returns to main screen. In previous version the banner just showed, but game continued. Its huge annoyance right now, having to hit Continue every time the bug occurs.

It also aborts when you lose, still :(

• This version has network play restored, so hopefully somebody can test that.
• there are some small fixes related to hildon-games-wrapper and task switching as well