Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 1 post(s) |
Ruthless eficiency
BLACK SQUADRON. The Bastion
1
|
Posted - 2015.04.29 13:06:08 -
[1] - Quote
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. |
minni mitti
Demezes Enterprise Shadow of xXDEATHXx
0
|
Posted - 2015.04.29 13:17:58 -
[2] - Quote
same here |
Gumpy Bitterhawk
Tax Evaders.
7
|
Posted - 2015.04.29 14:14:28 -
[3] - Quote
Same here.
This isn't the first time ive had this issue with the Mac client either |
Raul Gavin
Applied Anarchy SpaceMonkey's Alliance
20
|
Posted - 2015.04.29 14:26:46 -
[4] - Quote
Yeah, so this bug is now worse in the new patch.
Up until now, all I had to do was make sure when I was closing one client that the "focus" went to a running program other than EveGǪbut yesterday when I did that my second client locked up anyway. Logging in this morning I now find that my launcher doesn't work.
I guess I will have to figure out this clone maker thing. I don't understand why I need to jump through all these hoops to play a game?
It's really lame.
|
Vincent Athena
V.I.C.E.
3341
|
Posted - 2015.04.29 16:39:11 -
[5] - Quote
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.
Know a Frozen fan? Check this out
Frozen fanfiction
|
Rufelza
Widowmakers
5
|
Posted - 2015.04.29 17:00:21 -
[6] - Quote
yeah this is what I have been experience since the Mozzy roll out. |
Radioactive Isotope
Rage of Inferno
4
|
Posted - 2015.04.29 18:02:41 -
[7] - Quote
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? |
Ryan Rs
Strange Energy The Bastion
27
|
Posted - 2015.04.29 19:45:05 -
[8] - Quote
If EVE fails to launch, you don't need to restart. Just open a terminal window and run "killall wineserver"
Before this patch, one of the main reasons quitting a client would freeze other clients is because the quitting client would delete the wine socket when it quit, even though that socket was shared by all the running clients. So all would freeze. The solution was to always force quit, so clients wouldn't get a chance to do any cleanup. That stopped working with this patch though. It's probably something equally dumb, but I haven't had a chance to debug it yet. |
Ruthless eficiency
BLACK SQUADRON. The Bastion
3
|
Posted - 2015.04.29 21:42:33 -
[9] - Quote
Ryan Rs wrote:If EVE fails to launch, you don't need to restart. Just open a terminal window and run "killall wineserver"
Before this patch, one of the main reasons quitting a client would freeze other clients is because the quitting client would delete the wine socket when it quit, even though that socket was shared by all the running clients. So all would freeze. The solution was to always force quit, so clients wouldn't get a chance to do any cleanup. That stopped working with this patch though. It's probably something equally dumb, but I haven't had a chance to debug it yet.
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! |
|
CCP Sledgehammer
C C P C C P Alliance
408
|
Posted - 2015.04.30 11:28:12 -
[10] - Quote
I can confirm that we know of this issue, it is with our partners at the moment. As I have advised everyone else experiencing this issue, using Clonemaker to create clones of your master EVE client stops this from being an issue. You can find clonemaker and full instructions here
Graphical QA Analyst | EVE Quality Assurance | Team TriLambda
|
|
|
grumpychops
Non Nobis
4
|
Posted - 2015.04.30 13:49:56 -
[11] - Quote
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. |
Tahnil
Sirius Fleet AXIOS.
57
|
Posted - 2015.05.01 09:51:37 -
[12] - Quote
Confirming this issue. KIlling wineserver via activity monitor app (in CPU view) is a temporary fix. |
Kuda Timberline
Alea Iacta Est Universal Brave Collective
9
|
Posted - 2015.05.01 22:29:08 -
[13] - Quote
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.
Kuda Timberline
Co-host Capstable Podcast
|
Kuda Timberline
Alea Iacta Est Universal Brave Collective
9
|
Posted - 2015.05.02 13:25:59 -
[14] - Quote
CCP Sledgehammer wrote:I can confirm that we know of this issue, it is with our partners at the moment. As I have advised everyone else experiencing this issue, using Clonemaker to create clones of your master EVE client stops this from being an issue. You can find clonemaker and full instructions here
I'm running into problems running Clonemaker. Every time I launch it, I just get an error that the app is damaged and should be trashed. I've re-downloaded and unstuffed the app, but just keep running into the same issue. Anyone else seen this and is there a workaround for this workaround. ughh
EDIT: I found my own work around after searching around for a few min. I'ma bad and should have done that first..
The workaround is to allow you Mac to run application from everywhere. This can be found in the System control panel under security.
BEWARE: I would only suggest using this feature when needed, then once you are done using clonemaker re-enable the setting to only run apps from App Store and identified developers.
Hope this helps.
Kuda Timberline
Co-host Capstable Podcast
|
Frightstar
Rolling Static Gone Critical
9
|
Posted - 2015.05.02 16:27:22 -
[15] - Quote
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. |
Ian Blackbird
Industrie und Handels Konsortium
8
|
Posted - 2015.05.13 09:01:23 -
[16] - Quote
CCP Sledgehammer wrote:I can confirm that we know of this issue, it is with our partners at the moment.
Any News on that Issue? Will it be a matter of Weeks? Months? Years? I'am not mad about it, just a bit curious... |
Amarisen Gream
Divine Demise
75
|
Posted - 2015.05.14 05:28:12 -
[17] - Quote
(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.
xoxo
Amarisen Gream
|
sama kanaan
The Returners Hideout Confederation of xXPIZZAXx
0
|
Posted - 2015.05.27 11:03:09 -
[18] - Quote
Eve for MAC OS really needs a overhaul.
CCP seems too spread out, they have all this stuff on their plate, from other games, to rebalancing every item in game, to all the other things they are implementing. Yet, EVERY single day people using MAC OS are dealing with really crumby code that requires multiple resets of laptops, launchers, requires FORCE QUITTING applications over and over. (Similar to task manager)
What do we need to say to get some IT support from CCP? What do we need to do? If we have multiple toons and we cannot even run them with ease, what are our options other then these 'work arounds' and 'fixes' people discover. Fix. The. Issue. |
Kuda Timberline
Alea Iacta Est Universal Brave Collective
9
|
Posted - 2015.06.27 18:12:46 -
[19] - Quote
CCP Sledgehammer wrote:I can confirm that we know of this issue, it is with our partners at the moment.
Any Update? If this is still with your partners you should probably fire them and hire new partners...
Kuda Timberline
Co-host Capstable Podcast
|
Ohnesorge
Hydra Inc. Synergy of Steel
0
|
Posted - 2015.07.11 16:28:32 -
[20] - Quote
Any Update? |
|
Hizumi Mizushiro
Earth Alliance Expeditionary Force
1
|
Posted - 2015.07.27 17:12:52 -
[21] - Quote
I'm surprised no ones figured this out yet; Theres a relatively simple workaround / solutions which could be implemented by CCP with relative ease. I've been using this since the problem occurred in Scylla.
Since the migration to the shared cache in Scylla, not only was the multi client cache shared into one directory, the wine socket was also put into the shared directory, which is the crux of the issue.
Launching multiple clients will reuse the wine socket, which is not a problem.
Closing one of those clients also closes the socket, so when other clients try to read/write to the socket, they appear to be dead.
Best i can figure the reason why the wine server appears stuck and needs to be kill -9'd in order to relaunch it is because its counter of open clients != closed clients, so the process remains active (though it could just be another problem related to an incomplete socket.close() call).
Workaround as follows:
- Open launcher
- Launch Client 1
- Navigate to shared Cache DIrectory [ ~/Library/Application Support/EVE Online ]
- Locate a directory named similar to wineserver-uuid-username
- Rename it to whatever you want
- Launch Client 2
- ???
- Profit!
The launcher will always regenerate the original folder name on every client launch, so any number of clients can be launched via this method by simply renaming the regenerated folder to a new name.
I have no idea why the generated uuid in the directory name is the same every time, it appears to be a mac address, but it doest match any of my interfaces.
Quick CCP solution would be to actually generate a uuid in the directory name on client launch + socket creation vs reuse of same socket.
Proper CCP solution would be to cross check whether it should actually run socket.close() on client quit if multiple clients are open vs just a deallocate ( Disclaimer: I know jack about how wine internals actually work )
Sorry for keeping this a 'secret' for so long. I honestly thought others had figured this out by now since it has been nearly 4 months.
=== CAVEAT ===
Almost forgot to put this in:
DO NOT OPEN IGB
IGB seems to do voodoo to the socket to generate a new window, but it cannot connect to the socket since the directory has been renamed ( doesn't affect game since socket was already open and fs changes on an os level won't affect data read/write ) |
Quazar Doosan
Blue Tridents
0
|
Posted - 2015.08.08 00:17:15 -
[22] - Quote
I was stoked by Hizumi's workaround but for that caveat... using the IGB all the time.
Also, FWIW... I leave a Terminal open so it's just up-arrow and enter to reissue `killall wineserver` which is a little bit handier than finding something in the Activity Monitor.
|
Gavascon
need more power inc. Murder By Numbers Alliance
0
|
Posted - 2015.08.24 00:34:05 -
[23] - Quote
i had filed a bug report regarding this problem on 6/17. ccp responded 2 days later - but never notified me.
revisited the bug report today (8/23) the advice they provided was contained in a wiki: https://wiki.eveonline.com/en/wiki/Multiple_clients none of the "fixes" seem acceptable. all the suggested solutions have issues.
today, had 2 clients running. playing station games with 4 war targets on station. when main toon suddenly "lost connection". of course, 2nd account "white" screened.
had to completely restart computer to re-enter game. during that time....ship destroyed. i'm sure CCP will replace the lost ship. not sure if they will completely accept the responsibility for the loot drop, deleting the loss mail, adjusting the war report, replacing lost skill points (because it was a t3) and rescinding bounty payouts - although that would be the right thing.
am very disappointed in the programmers at CCP who have allowed this problem to exist for such a long time without a viable solution. instead allowing us mac users to be inconvenienced while our PC "buddies" enjoy the game as intended.
|
Gavascon
need more power inc. Murder By Numbers Alliance
0
|
Posted - 2015.08.24 00:40:19 -
[24] - Quote
oops, didn't mean to post twice |
Bishamon Katani
Seven Gods of Fortune
5
|
Posted - 2015.08.24 17:16:14 -
[25] - Quote
CCP Sledgehammer wrote:I can confirm that we know of this issue, it is with our partners at the moment. As I have advised everyone else experiencing this issue, using Clonemaker to create clones of your master EVE client stops this from being an issue. You can find clonemaker and full instructions here
The link to clonemaker on that page is broken. The link is:
http://content.eveonline.com/www/tools/EVE_Clonemaker_rev6.zip
But on trying to load it, I get this:
Quote:ERROR
The request could not be satisfied.
CloudFront attempted to establish a connection with the origin, but either the attempt failed or the origin closed the connection. Generated by cloudfront (CloudFront) Request ID: KJmnMjlEsv_LoIeEBLM3Anta0GOOFq7V4oh2dRSiV3_92QI4CNP9ow==
I'm really tired of Mac users being treated like crap. CCP seems to never test any patches or updates on Macs and use us as their beta testers. But by the time they get an issue fixed, the next patch has broken something else. |
Gavascon
need more power inc. Murder By Numbers Alliance
0
|
Posted - 2015.08.27 14:27:13 -
[26] - Quote
i used the link. the lines of code that need to be changed are:
CFBundleName EVE Online 2
and
PrefsFolderName EVE Online 2
you need to change each string value. the CF's are core framework procedure calls for bundlename and prefsfoldername.
but there's one fatal flaw with this.
each time the launcher for the copy is used it OVERWRITES the info.plist file and resets it to the original settings. meaning: BEFORE ACTUALLY ENTERING EVE THE CODES HAVE TO BE CHANGED and MUST BE DONE EACH TIME THE LAUNCHER FOR THE COPY IS USED
you can use the 2nd launcher and log in....but do NOT click "play" before changing the info.plist file!!!
CCP, this a royal PITA. if any player closes the 2nd launcher a few times a day, then the info.plist file has to be changed a few times a day.
please, please please fix this!!! |
Sol Nieghtder
Exclusion Cartel The Kadeshi
4
|
Posted - 2015.10.04 20:13:12 -
[27] - Quote
The "quick fix" i have been using seems to work well. Use the ESC menu => Quit Game but before the command can "process" regain focus on the first client loaded, yes you have to be QUICK. Whatever works right? |
Kuda Timberline
Alea Iacta Est Universal
9
|
Posted - 2015.10.15 14:55:25 -
[28] - Quote
Bump - Still looking for a resolution.
CCP Sledgehammer wrote:I can confirm that we know of this issue, it is with our partners at the moment. As I have advised everyone else experiencing this issue, using Clonemaker to create clones of your master EVE client stops this from being an issue. You can find clonemaker and full instructions here
Kuda Timberline
Co-host Capstable Podcast
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |