Forums » Linux

vendetta process hang on exit

Nov 11, 2011 Googie link
When I exit the game, quit, everything appears as per normal. I have noticed that the vendetta process is still resident and taking 25% on an X4, so one CPU.. For every time I load game and exit (and still no problems with playing game at all, no error messages) there is a vendetta process still running and consuming CPU time. When I noticed this I had 4-5 processes running, since I was changing video settings for a new video card and exiting game, thinking this was necessary.

When I was playing for some time on Ubuntu 10.10 with an onboard ATI chip video card, this problem did not exist. I only noticed this problem present after I had updated to 11.10 AND also installed a new GTX560 Fermi. I am using the latest proprietary drivers, 285.05.09. I did notice that this latest driver update is supposed to fix some games hanging on exit.....

soooo? Any ideas? Anyone have this problem before? Recommend where I start to look for the source of the problem? I'm not sure if this is a vendetta problem or an Nvidia driver issue.
Nov 14, 2011 abortretryfail link
VO doesn't do this on my Linux box. ArchLinux with Xorg 1.10.4, and ATI's catalyst drivers 11.10 or on my laptop with intel video (dont know the versions)

I'd let Nvidia know about it.
Nov 27, 2011 Infinitis link
The same problem here.
Dec 07, 2011 Mick the Mighty link
I haven't played in a while, and chose to install LinuxMint 12. I installed the nVidia driver, and seems to have it working ok on my computer. I have installed Vendetta - AMD64 version, and notice the same thing, it doesn't close properly. LinuxMint, the nVidia drivers, and VO are updated.
Dec 21, 2011 Captain86 link
Fresh install of Ubuntu 64 11.10

Same problem

Freezes on exit or freezes on quit

Have to force quit, but this did not occur on ubuntu 10.10 which worked perfectly

Also many resolution selections for VO are not available as with 10.10

However the resolution selections exist in the actual Nvidia display settings but not in VO
Not sure why ?
Dec 23, 2011 abortretryfail link
Maybe this is a Ubuntu issue?
Dec 23, 2011 Captain86 link
Resolution settings in VO now appeared for no apparent reason so that is fine now, but I don't know why.

Freezes on exits still occur and I need to force quit
I'll try some other OS's and report back, but others in chat have reported that some Mac and Windows users also are experiencing this topic.
Dec 26, 2011 Captain86 link
After hosing my installation with settings that caused OS failure I reinstalled and I think I have the freezing issue solved, however this does not solve other OS's freezing topics but only for me on Ubunty 11.10

This time the fresh install of Ubuntu 11.10 with NO Gnome 3 classic install or LXDE or anything else just Unity by itself.
I noticed right away that the default Nvidia restricted driver version 173 was jittery but also not causing the exit on freeze

I installed the latest Nvidia restricted (non-free) driver and still no freezes

I installed compiz-settings-manager and went to Unitilty / Workaround / and checked (Legacy Full Screen Support) this will let the top bar of Unity be hidden as it use to be able to do with Gnome to hide the top bar so that it doesn't eat the uppper portion of the VO screen

Anyhow moving on

So fresh install, latest Nvidia driver, compiz-settings-manager and VO is running good and exits properly

I cannot re-duplicate the freezing thus I assume it must be something with the Gnome or LXDE installation when I was attempting to rid myself of using Unity.

Anyhow FYI for anyone using Ubuntu 11.10 and getting freezing on exit with Gnome or LXDE this might at least lead you in the right direction to fix it.

This won't help anyone with Windows or Mac OS when freezing on exit
Dec 26, 2011 Captain86 link
Scratch that, still freezing on exit.

For not reason , no updates, nothing changed on the system.
And it's freezing again so likely had nothing to do with Gnome etc.

It just started doing it again, Anyhow FYI
Dec 28, 2011 Ducky link
I'm getting a segfault when leaving vo. Settings don't apply, I have to agree to EULA every time, but it doesn't stick around in memory.

Debian Wheezy (testing)
2.6.38-2-amd64 kernel
8G ram
nVidia 9600GT using driver 275.09.07
no compiz, just dwm for my wm on xorg 1.9.5 =)
Dec 30, 2011 bonzwogi link
I'm also getting a segfault and/or hang on exit. In fact, if I click 'Quit' it segfaults, and if I press 'Escape' it hangs.

Vanilla Ubuntu 11.10
3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Intel® Core™ i7-2670QM CPU @ 2.20GHz × 8
GeForce GTX 560M/PCI/SSE2
Dec 31, 2011 bonzwogi link
With Vendetta 1.8.205, it no longer crashes when I click 'Quit'!

Unfortunately, it still doesn't close properly. Now, both clicking 'Quit' and pressing 'Escape' cause the game to hang -- whether or not I change video options.
Jan 04, 2012 Captain86 link
I have done some more tested and I don't even have to login but only need to go to the login screen and then exit/quit; and it freezes on exit directly from the login screen in windowed mode.

I have to force quite.
However, In full window mode the it will exit the screen correctly but vendetta is still running in the system monitor; and jumps to 100% and eventually maxes out to 200% on both cpu's then settles down to around 40%

If I try to run vendetta again in full window mode thinking that it has quit it will be running multiple instances of VO in the system monitor if I do not force quite all of them individually so although the screen does not freeze in effect it's still the same cause it's still running and does not quit

Same on my other machine with fresh intall of Ubuntu 11.10 and NO plugins on VO either.

Anyhow FYI
Jan 06, 2012 Captain86 link
Here is the error log I'm not sure this tells me anything about why it freezes on exit or stays running in the backround but here it is:

I deleted everything and just started and exited so we have only limited text:

Setting up signal handlers...done.
[Fri Jan 6 16:52:21 2012] Found driver: "Open Sound System driver". Type 1, Version 10.1. Load @0x00d77c10
[Fri Jan 6 16:52:21 2012] Instantiate address: 0x7fc5086191a0
[Fri Jan 6 16:52:21 2012] Found driver: "OpenGL Reference GKGL driver". Type 5, Version 92.0. Load @0x00d79750
[Fri Jan 6 16:52:21 2012] Instantiate address: 0x7fc5083fa060
[Fri Jan 6 16:52:21 2012] Found driver: "ALSA driver". Type 1, Version 10.1. Load @0x00d7ca40
[Fri Jan 6 16:52:21 2012] Instantiate address: 0x7fc507d678d0
ALSA initialized: 44100Hz, 16bit stereo, 92ms latency (16 periods x 256 samples)
[Fri Jan 6 16:52:22 2012] load_sample_ogg: Couldn't open sound/mission.updated.ogg (mission.updated)
[Fri Jan 6 16:52:22 2012] load_sample: Couldn't open sound/mission.updated.ogg (mission.updated)
[Fri Jan 6 16:52:22 2012] load_sample_ogg: Couldn't open sound/nfz.warning.enter.ogg (nfz.warning.enter)
[Fri Jan 6 16:52:22 2012] load_sample: Couldn't open sound/nfz.warning.enter.ogg (nfz.warning.enter)
[Fri Jan 6 16:52:22 2012] load_sample_ogg: Couldn't open sound/nfz.warning.leave.ogg (nfz.warning.leave)
[Fri Jan 6 16:52:22 2012] load_sample: Couldn't open sound/nfz.warning.leave.ogg (nfz.warning.leave)
/dev/js0: No such file or directory
Found joystick 'Saitek Cyborg X (/dev/input/js0)'
numaxes = 7
numbuttons = 14
/dev/js1: No such file or directory
/dev/input/js1: No such file or directory
/dev/js2: No such file or directory
/dev/input/js2: No such file or directory
/dev/js3: No such file or directory
/dev/input/js3: No such file or directory
Found 1 joystick(s)
Input driver initialized.
allocated pipes: 17->16, 19->18
Voice Chat loaded.
Voice Chat initialized.
Loaded plugin 'AutoJett'
Loaded plugin 'AutoRR'
Loaded plugin 'guildnotify'
Loaded plugin 'honk'
Loaded plugin 'InfiniTurbo'
------------
TCS loaded successfully!
------------
Loaded plugin 'Kyonko-tcs-plugins-04af8ab'
Loaded plugin 'score'
Loaded plugin 'TargetBinds'
Loaded plugin 'targetless'
Loaded plugin 'vzoom'
[Fri 06 Jan 2012 04:52:29 PM EST] Flight-Assist mode enabled.
[Fri 06 Jan 2012 04:52:29 PM EST] Auto-Aim enabled.

Doesn't look like it tells anything about quit errors, only some startup errors which may not mean anything at all