Macintosh

I am noticing when I first start there is unusual number of crashes. Typical run of 3 separate client on the Machine, which pre Kronos never caused a problem. Now I frequently get a "Buffer Overrun Error" and one or more of the clients will crash.
Also of note all my old Clone Maker Scripts I used in the past no longer worked. But I noticed that now you can launch multiple instances like Windows Machines can with the launcher. This is nice as no longer need 3 different Pin Launchers for running all 3 clients.
My Hardware is
iMac OS X 10.9.3
Processor 2.7 Ghz Intel Core i5
Memory 8GB 1600 DDR3

I am having the same issue.

i experienced a similar issue - reproducable on two different machines.
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!

I got freezing-issues before - but they where gone in rubicon. now, with kronos, they appear again as described.

Hardware:

Computer #1:
Apple iMac "Core i5" 2.8 27-Inch (Mid-2010)
12 GB RAM
10.9.3
ATI Radeon HD 5750 1 GB

Computer #2:
Apple MacBook Pro "Core i7" 2.2 15-inch (Late-2011)
16 GB RAM
10.9.3
AMD Radeon HD 6750M 512 MB

Confirmed, my clients did not crash while running in full screen mode. 2011 MacBook Pro, 2.8 i7, 8 GB, OSX 10.9.3

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

Confirming this. Every single time.

As before, optimizing for memory makes dual-boxing on the Mac much more reliable. It doesn't get rid of the intermittent freezes, it just makes them a lot more intermittent. But regardless, the instant I quit one client the other freezes hard.

27" iMac late 2012
OS X 10.9.3, all patches applied
24GB RAM (which also makes the intermittent crashes less frequent)
Running in windowed mode, 1600x1200

I seem to have a problem where if one client is closed in any way, all the other clients freeze

Also have the same problem of all clients freezing when quitting one client.

Running on a rMBP, 2.6 GHz and 16 GB of RAM, latest public Mac OS X build.

Typically clients seem stable for me though.

I'm going to add my voice to this, and a more detailed post is forthcoming from me momentarily. However, I believe that the core of the issue is that multiple EVE Online clients are trying to access the same "Application Support" folder for reading and writing their preferences, and they're stomping all over each other, and that THIS is what's causing the freezes.

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. The analogous situation, here, is if CCP Karkur opened her private diary at home at night only to discover that CCP Guard and been writing in it as though it were his private diary, instead. CCP Karkur, I am reasonably confident, would start freaking out.

The short form of my proposed solution is that the Launcher must be reprogrammed to NOT revert changes to a certain "info.plist" file if it only detects minor string changes in a couple of key values: {key}CFBundleName{/key} and {key}PrefsFolderName{/key} This reprogramming of the Launcher must be done before this release gets pushed to Tranquility or CCP and Transgaming will seriously inconvenience every single Macintosh multiboxer in EVE Online.

Again, a more detailed post from me is forthcoming, and yes, the sky is falling.

[Continued from previous post.]

A lot of the reports here suggest that Game Clients freaking out only occurs when one of the Game Clients quits. So, an alternate explanation is that when one Game Client quits, the relevant files inside the “Application Support” subfolder are marked as closed, and the other Game Clients that were relying on them can no longer access them because they weren’t programmed to deal with a situation where a program other than itself has closed a file that it was working on. The analogous situation, in that case, is that two surgical teams are each operating on their own patient but sharing the same surgical tools and operating room. (Let’s set aside germ transmission between patients.) As soon as one surgical team finishes their operation, they put away the shared surgical tools. The other surgical team that was relying on those tools suddenly discovers that those tools are gone and locked up, and they freak out. The end result is that their patient dies. This is what I believe is causing a lot of the Singularity Macintosh multiboxing issues being reported here.

Whether the clients are freezing on a second client being started or on any client quitting, the basic issue is the same: it is extremely bad for two applications (or two copies of an application) to point to the same Application Support subfolder at the same time unless they were explicitly designed and programmed with this in mind.

This is extremely important. It bears repeating.

It is extremely bad for two applications (or two copies of an application) to point to the same Application Support subfolder at the same time unless they were explicitly designed and programmed with this in mind.

The workaround is to start the Launcher, let it revert any changes it finds, and then when the Launcher reports ready, re-edit the info.plist files, and then click Play on the Launcher. This is extremely inconvenient for Macintosh multiboxers because it means that we have to do multiple file edits every time we launch the game instead of every time we patch.

---

CONCLUSION AND TL;DR:

The following conclusions must be passed to any member of CCP or Transgaming who owns this product feature or is otherwise directly responsible for implementation:

The easiest solution is to reprogram the Launcher so that it excludes “info.plist” from it’s integrity checks (or whatever they’re called). The Launcher must not revert any manual changes made to info.plist. Failing this, the Launcher must have an input somewhere that asks “Are you a multiboxer? If so, then what would you like to call your Application Support subfolder for this copy of the client? This name can be any valid Macintosh folder name, but please note that EVE Online tends to freeze if multiple copies are pointing to the same folder, so please choose a name for this client that isn’t used by your other clients.”

[edit] It would also be very nice if we would be allowed to start the game client directly without having to go through the Launcher, but this is optional so long as the Launcher stops reverting info.plist. [/edit]

If this is not how you intend for us to multibox on a Macintosh, then we will need explicit, simple, clear, “Explain Like I’m Barely Computer Literate” steps on how to run multiple simultaneous EVE Online accounts on a Macintosh. Whatever this method is, it must actually have been used by a relevant member of CCP or Transgaming to play multiple EVE Online accounts on a Macintosh.

[edit] I also suggest having a Macintosh multiboxer at CCP or Transgaming compare notes with a Windows multiboxer at CCP or Transgaming, because I suspect one side might be making incorrect assumptions about how the other side multiboxes. Windows is not Mac OS X. [/edit]