Menu

#15 3.2.2 Failing to reset resolution on exit, zombie processes

open
COW (2)
5
2007-07-20
2007-07-20
Caydel
No

Hello.

I guess I will do the honor of posting the first bug. I recently installed netrek-cow-client v. 3.2.2 on my Ubuntu Linux install.

I am having 2 issues:

1. The program fails to restore my screen resolution to 1280X1024 on exit, leaving it at 640X480 or whatever the game uses.

2. After quitting, there are often defunct zombie processes running in the background that have to be manually killed. The processes are 'netrek(defunct)'

Let me know if there is any way I can provide you with debug information.

Discussion

  • Caydel

    Caydel - 2007-07-20
    • assigned_to: nobody --> quozl
     
  • Caydel

    Caydel - 2007-07-20

    Logged In: YES
    user_id=1555016
    Originator: YES

    Assigning to quozl, since I am pretty sure you maintain this client, correct?

     
  • James Cameron

    James Cameron - 2007-08-09

    Logged In: YES
    user_id=19261
    Originator: NO

    Apologies for the delay.

    1. the resolution used by the program is 1024x768, and it is programmed to restore to what you had before if it can. If it cannot it reports this to stderr stream, which will either be displayed on a terminal window or sent to a log file in your current directory.

    1.a. please look for the stderr output and tell me what it says. You may have to start the program from a terminal window.

    1.b. as a workaround, you may either add "FullScreen: off" to a file .xtrekrc in your home directory, or use something like "gvidm 1280x1024" on exit manually.

    2. the only processes that are supposed to be created are the single process corresponding to the game window, and a process for use by a shell feature accessed from within the game.

    A defunct process in Linux is caused by the parent process not asking the operating system to tell it the final exit status of the child process it started. A defunct process has no resources, and consumes nothing on your system except a tiny amount of memory and space on the displayed process list.

    2.a. please describe how you started the program. This may tell me what process is responsible for cleaning up the defunct process entry.

    2.b. please describe how you quit the program. There are ways to quit that may not have been handled in the design.

    2.c. please reproduce the problem and capture the text output of the "ps axfw" command, so that I can see what these netrek processes were caused by. If possible, also capture for comparison the same "ps axfw" command while the game is running, and then after it quits.

    Thanks.

     

Log in to post a comment.