Macintosh

Every time that I've had 2 clients running and quit one the other will freeze. After force quitting the frozen client the launcher no longer succeeds in launching a new one. The only temporary fix I've found is a system restart.

Upon trying to launch with cider(which failed) I noticed this: Applications/EVE\ Online.app/Contents/Resources/EVE\ Online.app/Contents/MacOS/cider ; exit;
wine client perror:0x0: write/writev: Bad file descriptor
logout

Using launcher 2.2.878305 on OS X 10.9.5
Cache was cleared and didn't seem to help.
This was post Mosaic patch only.

Same here.

This isn't the first time ive had this issue with the Mac client either

Edit: The problem wich the OP describes started occurring again since todays patch. Please have a look at this ccp...last time this problem occurred it took literally over a year to find the problem, and this problem combined with ****** internet means i have to restart my Mac every 30minutes or so, its already driving me nuts :s

Ive seen this bug reported many times, but I have never seen it. I just ran 3 clients at once last night, no issue at all. I have no idea what I am doing right, but it must be possible to do it, as I am doing it.
The only thing I can think of is I use clones made with the Eve clonemaker.
Also, I always run in windowed mode, and switch from one client to the others via the icons in the dock.

By the way, using clones does remove one hoop you have to jump through: The clones bypass the launcher.

Same here as well. Running on a 2014 iMac and i would always have to force quit my clients before the patch to stop them from freezing the other clients. But now with the latest patch Force quiting no longer is a good work around for avoiding the freezing of the other clients.

Worst of all is that it stops the further launching of new clients until you restart your machine. Its becoming very aggrevating haveing to restart my machine every 30 mins or so. Can we please get a CCP person to confim they see this thread? Any info or bug reports that we can send to help?

This worked beautifully in terms of a work around that didn't require a restart. After executing "killall wineserver" i was able to launch clients successfully again. Thanks Ryan Rs!

With the latest update, there is a new twist to this issue. Force quitting the client doesn't completely quit it. Due to running multiple clients, I often have to force quit other clients when they freeze, due to quitting another. Yesterday, I noticed that the client would not restart. I then force quit all my clients. Then none of the clients would restart. I run on multiple computers, so I was surprised to see on my other computer that the clients that I just force-quit still had their chars logged into game. I scrolled through my activity monitor and noticed the task "wine server" was still running. I killed the task and all the chars on the previously force-quit clients logged out (I received the notification on my char on the other computer).

This issue repeated itself many times yesterday. Force quitting wine server seems to fix it.

Same here... this issues has been going on with me for over 1-2 years now through multiple OS rebuilds. There was also a similar bug with the launcher where you could only get it to close, w/o crashing, if you hid all other windows and ONLY closed the launcher by hitting the close window button in the top left corner. As far as the clients go, you used to be able to avoid the crash if you hid all other windows when quitting a client and also closed them with the close window button in the top left. All other forms of quitting the app seemed to result in a crash. This is no longer working as of the Mosaic patch. Client freezes every time another client is quit regardless of what windows are showing or how you quit the app.

As an IT guy (I'm PC now, but was a former Mac Certified Tech at my last job) I know the importance of documentation and will do my best to give as much detail here as possible.

First this problem started over a year ago, I wish I could remember what the offending patch was. At the time I was using Mac OS 10.9.x. This is an infuriating problem to deal with every time you quit the client. Remember... CCP doesn't have the tools to create a client that will let you switch characters without quitter the client, so you end up getting a crash every time you need to log a new character. I can only imagine the number of players sessions this has cut short, or even people who have quit the game because the Mac client just doesn't work. Well I decided to give CCP the benefit of the doubt and here are the procedures I've tried.

Once I first discovered the crash under 10.9 my fist action was to delete EVE and do a full re-install. This was unsuccessful.

2nd step was to completely wipe my computer, do a fresh install of 10.9 and a fresh install of EVE. This too was unsuccessful.

3rd step was to completely wipe my computer again, downgrade to a fresh install of Mac OS 10.8 and a fresh install of EVE. This too was unsuccessful.

As I mentioned early, I had found a work around to this problem prior to Mosaic. The work around goes as follows:

Open multiple EVE clients from the installer.
Close the installer w/ the close window button in the top left (other forms of quitting caused a crash)
Both clients seem to work fine together except for the typical texture errors that make space look like a green cube.
Once it is time to close I client you must hide all other apps and windows and only close the client you want closed. If any other client windows are visible when you close the first, you would get a crash.

This process no longer works, and my insanity has brought me here to document it. Now that the client crash every time one is closed you can no longer even launch a new client. When you hit PLAY on the launch, it says launching, then nothing ever happens. Here is the error I've found when the client fails to launch after a freeze:

launcher[1320]: wine client perror:0x0: write/writev: Bad file descriptor

If I log out and back in the clients will still not launch from the launcher. It requires a full restart. ONce I restart I'm able to get the clients open, but even when doing my old "hide all windows" trick it still crashes. Here is the full log from that final crash. It seems the second client doesn't actually crash till you un-hide the window and look at it. I know this because I can still hear station noises and logout chimes. Here is the log for the final crash of the second client once pulled to the front:

http://pastebin.com/Lxn7FFLc

From what I can tell from where I find my ship, the actual disconnect from CCP's servers doesn't occur during the freeze, it occurs when you Force Quit the app.

I really hope this helps. This is a serious problem for the Mac community.

If you terminate the "wineserver" process i am able to start a new client.

However the old fix for dual boxing to prevent both from crashing (tabbing to a non-eve window, and then going back to one client to close it) no longer appears to work. If i close one, both will crash no matter what i do.

(I am in a bad mood. Please forgive me if I seem pissed off)

1: use clonemaker
2: if clonemaker says it is "broken" r-click show package and find the "script". Open that an run it.
3: IGB has a few issues as well as other things that lock the game up. Open activity monitor and start killing your wine servers. That will allow you to restart your clients.

4: there's like 9 post already on this topic. I know b/c I have posted in like 8 of them.

Any Update? If this is still with your partners you should probably fire them and hire new partners...