These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Macintosh

 
  • Topic is locked indefinitely.
Previous page12
 

Problems encountered running multi-Box on iMac

First post
Author
Previous Topic Next Topic
Hunter Ace
Fuctifino
#21 - 2014-06-13 15:04:13 UTC
I don't know what cloneMaker is, but I will echo others here. Since the patch, If I'm running two clients and I close one, the other freezes and I have to Force Quit the application and restart.

I'm on a 27' iMac, OS X 10.9.3, 3.06 Core 2 Duo, 8 GB of ram, ATI Radeon HD 4670 256 MB
beakerax
Pator Tech School
#22 - 2014-06-14 03:14:16 UTC  |  Edited by: beakerax
Alisyana wrote:
Confirmed, repeatable bug. Wineserver crashes when 1st client is killed, causing the freeze on all remaining clients.


Seamus Donohue wrote:
When one client tries to do something with "Application Support", it does something to the contents of "Application Support" that causes the other client to freak out.

Well done sirs/madams.

I'm not 100% on the internal workings of wine or cider, but here's what seems to be happening:

When the EVE client starts, wineserver generates and opens two socket files in ~/Library/Application Support/EVE Online if files at those paths do not already exist. When a client exits, both files are quite likely to be closed and destroyed… even though wineserver and the other clients still need them in order to function.

If each EVE client can be attached to different socket files (say, by renaming their parent directory each time it is generated), they can be exited safely. I was able to reliably run and quit multiple clients like this.

e: I've attempt to submit a bug report to this effect. I have no idea if it went through.
Seamus Donohue
EVE University
Ivy League
#23 - 2014-06-14 04:52:08 UTC  |  Edited by: Seamus Donohue
CCP Sledgehammer wrote:
Hi guys,

Sorry I haven't been active in this thread before now!

I want to reassure you that we and our partners are actively looking into this issue. I will update as and when I have more information.

A show of hands, if you'd be so kind.... Please EVE Mail me if you are experiencing this issue and you use multiple EVE client installs set up with CloneMaker

Thanks for your patience, everyone.

"'EVE Clonemaker.app' is damaged and can't be opened. You should move it to the Trash."

beakerax wrote:
Well done sirs/madams.

I'm not 100% on the internal workings of wine or cider, but here's what seems to be happening:

When the EVE client starts, wineserver generates and opens two socket files in ~/Library/Application Support/EVE Online if files at those paths do not already exist. When a client exits, both files are quite likely to be closed and destroyed… even though wineserver and the other clients still need them in order to function.

If each EVE client can be attached to different socket files (say, by renaming their parent directory each time it is generated), they can be exited safely. I was able to reliably run and quit multiple clients like this.

e: I've attempt to submit a bug report to this effect. I have no idea if it went through.

Well done. If true, that would explain what we're seeing.

Survivor of Teskanen.  Fan of John Rourke.

I have video tutorials for EVE Online on my YouTube channel: http://www.youtube.com/user/SeamusDonohueEVE
Invisusira
Escalated.
OnlyFleets.
#24 - 2014-06-14 13:02:12 UTC
Do we need to use Clonemaker? I've just been running a second client straight from the launcher, with zero problems up until now.

EVE Music
beakerax
Pator Tech School
#25 - 2014-06-14 21:26:34 UTC
Invisusira wrote:
Do we need to use Clonemaker? I've just been running a second client straight from the launcher, with zero problems up until now.

Based on the document that Sledgehammer linked it seems we are encouraged to clone the clients one way or another to prevent exactly this kind of problem. But given that Clonemaker apparently won't run and, as Seamus described, the Launcher automatically "fixes" (ie breaks) cloned clients anyways, I'd say that what we're meant to do is not really relevant.
Vincent Athena
Photosynth
#26 - 2014-06-15 02:12:42 UTC
I use the clonemaker, and used it to make 3 clones of the Kronos client. I can run all three, and 95% of the time have no problem. I can close one and the others keep running. They do access different "application support" files. I tested this by saving an overview setting in one clone, and finding it did not show up for another.

The bug I do have is the short freezes. One client will stop working for 10 to 200 seconds. Afterwards, I start getting graphics artifacts: buttons blanked out, ships turning white, stations turning yellow. If I restart the computer, the onset of these issues is delayed. I had one period, from June 5 to June 12, where I never saw the issue, just to have it return June 13.

For those getting the "Application damaged" message, check out https://forums.eveonline.com/default.aspx?g=posts&t=316715&find=unread.

Know a Frozen fan? Check this out

Frozen fanfiction
Mister Falcons
NF Plains
#27 - 2014-06-16 07:45:55 UTC  |  Edited by: Mister Falcons
I was prior to Kronos using CloneMaker. After I reported an issue and support rep recommended just using launcher and not the Clones that when I started having client issues with freezes both when exiting one. To test to see if as I suspected with was having a file access issue, I deleted all my old CloneMaker Clones and created 3 new clones. After that the freezing issues went away.
A reminder if you use CloneMaker, you should only run patch updates using the launcher, so my first start of the day I will start the launcher let it do any updates, then start my clones.I have using this method resolved 95% of the issues with multi-boxing on my iMac.
The only issue I have now is an occasionally about 5 minutes after I start 1 of the clients, usually the first Clone I started will get a Socket Closed error. But this is intermittently and once I restart the client, the issue does re-occur that session. I was told this was ISP issue, but not 100% sure if I agree, cause its always the first Clone that I started, and only affects that one Box, if it was ISP issue I would expect all 3 or 4 clients to have the issue, not just the first launched Clone.

CCP Sledgehammer wrote:
Hi guys,

Sorry I haven't been active in this thread before now!

I want to reassure you that we and our partners are actively looking into this issue. I will update as and when I have more information.

A show of hands, if you'd be so kind.... Please EVE Mail me if you are experiencing this issue and you use multiple EVE client installs set up with CloneMaker

Thanks for your patience, everyone.
Vincent Athena
Photosynth
#28 - 2014-06-16 10:53:27 UTC
Mister Falcons wrote:
....
The only issue I have now is an occasionally about 5 minutes after I start 1 of the clients, usually the first Clone I started will get a Socket Closed error. ....

I had that exact same issue yesterday. After about an hour of running 3 clones, the first one got a socket closed error, the other two were fine.

Know a Frozen fan? Check this out

Frozen fanfiction
S'No Flake
Native Freshfood
Minmatar Republic
#29 - 2014-06-17 12:19:02 UTC
I have the same issue with one client freezing when i close the other one. I'm playing from a macbook and duplicating clients will leave me with barely any free space on my HDD.

I'm wondering if keeping the plist files outside of the eve app folder and creating symlinks to them before launching the client will still work.

In theory it should... assuming the plist file it's checked only when application it's launched.
Dersen Lowery
The Scope
#30 - 2014-06-17 15:30:01 UTC
Seamus Donohue wrote:
"'EVE Clonemaker.app' is damaged and can't be opened. You should move it to the Trash."


Even if you right-click and "Open?" That looks like Gatekeeper from here.

I gave up using Clonemaker when the Launcher came out because I got the message that it would take care of all that stuff behind the scenes. In fact it never was that good at handling multiple clients--I can't tell you how many times I had to rebuild my Overview--but it was better than this.

CCP Sledgehammer, are you officially recommending that we go back to using Clonemaker (and three Launchers?!) or do you just want some A/B testing?

Proud founder and member of the Belligerent Desirables.

I voted in CSM X!
The Tallman
The Scope
Gallente Federation
#31 - 2014-06-17 23:26:51 UTC
Alisyana wrote:
Ian Blackbird wrote:

multiboxing with 2 clients, both started from the EVE Launcher - no cloning script or other non-CCP tools/techniques used.
if i quit one of the clients, the other client freezes immediately - EVERY SINGLE TIME!



Confirmed, repeatable bug. Wineserver crashes when 1st client is killed, causing the freeze on all remaining clients.



Same problem, two clients running in windowed mode, when I quit one, the other crashes/locks up.
Hunter Ace
Fuctifino
#32 - 2014-06-28 13:17:12 UTC
I've found if I force quit one client (as opposed to quitting) the other won't freeze.

Has there been any other resolution to this issue?
DaCheat
ElitistOps
Deepwater Hooligans
#33 - 2014-06-28 19:30:53 UTC
Hunter Ace wrote:
I've found if I force quit one client (as opposed to quitting) the other won't freeze.


Same here. Thought it was a fluke at first, but now playing the guessing game to which client I'm closing will have to do. haha

OS: Windows 10 Home

Motherboard: MSI Z97A Gaming 7(MS-7916)

CPU:  Intel Core i7-4790K @4.00 GHz

GPU:  GeForce GTX 970

Memory:  16GB
Previous page12