Crack Attack! - Bugs: bug #15721, Running a server from GTK+ with...
You are not allowed to post comments on this tracker with your current authentication level.
bug #15721: Running a server from GTK+ with debug enabled causes lockup
Submitter: | Andrew Sayman <lorien420> | ||
Submitted: | Sun 12 Feb 2006 10:37:33 AM UTC | ||
Category: | None | Severity: | 4 - Important |
Item Group: | None | Status: | In Progress |
Privacy: | Public | Assigned to: | lorien420 |
Open/Closed: | Open | Operating System: | None |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
CC list is empty
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2006-02-12 | lorien420 | Status | None | In Progress |
Powered by Savane 3.13-d3ae.
Corresponding source code
When running a server from the GTK+ front-end, the game will lock up after a few seconds. The backtrace implies that the game-process is waiting for some sort of I/O signal from the GTK+ process. It's not clear entirely what's going on here, but it could be some of the console flavored output is screwing up the GTK+ code we've written. It could also be that our handling of GIOChannel is just wrong and it only comes up when we're pushing tons of text.
The general solution to this is going to be taken from the Mac Crack Attack people. I'm gonna make an Alert or Output class that can more intelligently handle the style of output we're looking for.