Opened 12 years ago
Closed 12 years ago
#1347 closed defect (fixed)
Game does not exit properly after a game
Reported by: | fabio | Owned by: | |
---|---|---|---|
Priority: | Must Have | Milestone: | Alpha 12 |
Component: | Core engine | Keywords: | |
Cc: | Patch: |
Description
Start 0 A.D. from a shell, start a game and then try to exit. The window close but it doesn't completely exit to the shell, you must press CTRL-C. Works OK on alpha 9.
Tested on current SVN on Ubuntu 12.04.
Attachments (2)
Change History (20)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
$ gdb ./pyrogenesis ... start a game, press ALT + F4 ... ... window close, but program doesn't exit ... ... CTRL+C ... (gdb) thread apply all bt
bt attached.
by , 12 years ago
follow-up: 4 comment:3 by , 12 years ago
Is that the full output of bt
? Can you also paste the console debug output? That should tell us which phases of the engine shut down have finished, if any.
comment:4 by , 12 years ago
Replying to historic_bruno:
Is that the full output of
bt
?
Yes.
Can you also paste the console debug output? That should tell us which phases of the engine shut down have finished, if any.
Attached.
comment:6 by , 12 years ago
Replying to Philip:
Do you have the
gamin
package installed, or the olderfam
?
Gamin 0.1.10-4 (from Ubuntu 12.04). Also note that I am building with:
--with-system-enet --with-system-mozjs185 --with-system-nvtt
using the Ubuntu provided libs.
comment:8 by , 12 years ago
Replying to historic_bruno:
Can you try building with the
--without-fam
flag, too?
It works fine with it.
Also note that without it the problem is reproducible only when quitting after a short time of game start. When quitting after a longer time the problem doesn't happen.
comment:9 by , 12 years ago
Milestone: | Alpha 10 → Alpha 11 |
---|
Is feedback enabled? The user report system is triggered almost immediately after the game starts, so it may be causing a problem. There's a delay on any OS because of that but it should only be 10-15 seconds at most.
If FAM is to blame, perhaps #1316 will resolve this.
comment:10 by , 12 years ago
Any chance some other threading issue may be at fault? Maybe FAM is not the problem but the symptom (if I'm not mistaken --without-fam
will both disable the hotloading mechanism on Linux and remove the processing thread, thus one less chance for deadlock).
comment:11 by , 12 years ago
Milestone: | Alpha 11 → Backlog |
---|---|
Resolution: | → needsinfo |
Status: | new → closed |
Summary: | game does not exit properly after a game → [NEEDS INFO] Game does not exit properly after a game |
comment:12 by , 12 years ago
Milestone: | Backlog |
---|
comment:13 by , 12 years ago
Milestone: | → Backlog |
---|---|
Resolution: | needsinfo |
Status: | closed → reopened |
Summary: | [NEEDS INFO] Game does not exit properly after a game → Game does not exit properly after a game |
This shouldn't be closed yet, it's still an active problem (in fact I encountered it a few days ago on an Ubuntu VM).
comment:14 by , 12 years ago
I marked it as "needsinfo" because the reporter of the issue hasn't replied to you in 2 months. But I can leave it open for now.
follow-up: 16 comment:15 by , 12 years ago
Still reproducible after the FAM disabling of some days ago. Strangely I was saying I cannot longer reproduce this but after many attempts it reappeared.
follow-up: 17 comment:16 by , 12 years ago
Replying to fabio:
Still reproducible after the FAM disabling of some days ago. Strangely I was saying I cannot longer reproduce this but after many attempts it reappeared.
Hmm, in that case I'd say a gdb backtrace is very important so we can see what if not FAM is responsible.
comment:17 by , 12 years ago
Replying to historic_bruno:
Replying to fabio:
Still reproducible after the FAM disabling of some days ago. Strangely I was saying I cannot longer reproduce this but after many attempts it reappeared.
Hmm, in that case I'd say a gdb backtrace is very important so we can see what if not FAM is responsible.
I still wasn't able to get a backtrace since it's very difficult to reproduce this bug.
Also, I have both alpha 10 (deb package) + build from svn tree. Strangerly I noticed that when I am able to trigger the bug in the svn I am later also able to trigger it in alpha 10. After a while it disappear on both... maybe it depends on some condition not strictly related to 0 A.D.?
comment:18 by , 12 years ago
Milestone: | Backlog → Alpha 12 |
---|---|
Resolution: | → fixed |
Status: | reopened → closed |
I am no longer able to reproduce it, supposing fixed. I'll reopen if needed.
Can you run it in
gdb
and break at the point it locks up, seeing what the call stack of all threads is?I can't reproduce on Ubuntu 11.10