Guild Wars 2

It went through a 2 minute download then nothing happened. Now when I click to open GW2 it just gives me an error "The application “Guild Wars 2” can’t be opened. -600" Not sure what happened but it seems the download failed miserably.

try to check the monitor activity if some other session is already running. force stop then restart.

worked for me.

If TreeRhino’s having the same problem as I am then the client doesn’t show up as something you can force quit. It’s like it doesn’t exist except you get this annoying error which assures you that it DOES exist… and you can’t do anything about it except reboot. Nothing fixes it for me yet.

Hypericon.6157:

try to check the monitor activity if some other session is already running. force stop then restart.

worked for me.

Seems to have worked.. at least so far. Thank you!

HBNole.4396:

If TreeRhino’s having the same problem as I am then the client doesn’t show up as something you can force quit. It’s like it doesn’t exist except you get this annoying error which assures you that it DOES exist… and you can’t do anything about it except reboot. Nothing fixes it for me yet.

Open your Applications folder.
Open the Utilities folder located in the Applications folder.
Open the app Activity Monitor located in the Utilities folder.
Type Guild Wars 2 in the search box in the Activity Monitor window.
Select Guild Wars 2 in the list of applications in the Activity Monitor window.
Click the little stop sign with an x button in the Activity Monitor window.
Confirm you want to quit it.

After update and crash within 30 min in EOTM, the game can’t be opened again. It never happen before. Restart? not yet, cause I have no mood now when I realise it crashes several times everyday.

A restart really isn’t necessary, it looks like there are three Guild Wars 2 processes that start up when you launch the game. When you get a crash, one of them never seems to end with the rest of the processes. This means you have to manually go in and quit that last process using activity monitor every time. Are you doing this and still experiencing the problem of not being able to start the game again?

Nageth.5648:

A restart really isn’t necessary, it looks like there are three Guild Wars 2 processes that start up when you launch the game. When you get a crash, one of them never seems to end with the rest of the processes. This means you have to manually go in and quit that last process using activity monitor every time. Are you doing this and still experiencing the problem of not being able to start the game again?

Negative, only one gw2 opened. And I remember that I could open two gw2 with different characters at the same time in the past.

I think you’re still misunderstanding. One of the new processes (maybe the one responsible for the TP) isn’t shutting down on crash. They’re all named “Guild Wars 2” but they’re not all the game engine that make all the graphics for the characters and worlds. Here is another example to help explain this better.

This is my dock running EVE Online (a cider port just like GW2). You may think I’m running 2 instances of EVE Online (running two accounts). I’m not, the left is the game, the right is the in game web browser (or in the activity monitor the one with the higher PID). We probably have the same thing going on here with GW2 but for the TP instead of for a full web browser.

Nageth.5648:

I think you’re still misunderstanding. One of the new processes (maybe the one responsible for the TP) isn’t shutting down on crash. They’re all named “Guild Wars 2” but they’re not all the game engine that make all the graphics for the characters and worlds. Here is another example to help explain this better.

True, but not complete. For reasons having to do with how Activity Monitor handles display of some kinds of processes and the particular way Cider is used by GW2 you will not generally see the cider process, but the wineserver one will show up. IIRC Dragon Age 2 does things slightly differently and you see both cider and wineserver there if it locks up. This means that killing the cider process may have to be done from Terminal with:

        killall -s -m '^cider$'