What happens to me is that EVE Client just Freezes (=no crash report generated?). Graphics freezes, music sticks like a broken CD, takes no input whatsoever, not even the window-buttons. And it needs be closed using 'Force Quit'. Happens so often cannot really play at all.

Please open /Users/Account Name/Library/Application\ Support/Eve Online/p_drive/

Attach "Win32 CrashReport" and "Win32_minidump.dmp" to a bug report and call it "For Konflikt : Mac Crash" or similar and I will endavour get this fixed as fast as i can :)

Cant find those files at ../p_drive/

What happens to me is that EVE Client just Freezes (=no crash report generated?). Graphics freezes, music sticks like a broken CD, takes no input whatsoever, not even the window-buttons. And it needs be closed using 'Force Quit'. Happens so often cannot really play at all.

Please can any of you describe the circumstances when the client crashes? Your assistance will mean that i am able to give the most detail to our programmers to fix this.

Are you undocking or docking? I was not
Do you have CQ enabled or ship spinning? Ship Spinning, CQ is the devil
Is there heavy graphical load? Not really, been getting 110fps or greater normally
What are your graphics settings? Pretty much all on low or disabled
Are you all using ATi Macs? Hell Yes (5770, 4870, 3870, but this time the client was on a monitor fed by the 5770)
What is your OSX version? 10.7.2, MacPro, 16GB ram

I apologize for the difficulties this issue causes and I really do want to get this resolved.

Crash dumps are the cornerstone of how crashes are resolved, without them it's simply not possible to fix the issue, luckily our new crashes tool helps a little but in some cases we need to see the crashes you are experiencing and are most important to you.

For the people who can't find the crash dump normally in the root of the P_Drive, please can you try a simple step to see if there are any dumps created.

1) Open Terminal from Spotlight
2) type "cd ~/Library/Application\ Support/EVE\ Online/p_drive/
3) next type "ls -R | grep .dmp"

If there are any dump files listed after step 3, take a look here too:
~/Library/Application\ Support/EVE\ Online/p_drive/Local\ Settings/Application\ Data/CCP/Eve

Again if you find a crash dump after crashing on TQ, ever, make a bug report call it "For Konflikt : Mac Crash" and I will do my best to crush all mac bugs, especially crashes :)

Please can any of you describe the circumstances when the client crashes? Your assistance will mean that i am able to give the most detail to our programmers to fix this.

1 Are you undocking or docking?
2 Do you have CQ enabled or ship spinning?
3 Is there heavy graphical load?
4 What are your graphics settings?
5 Are you all using ATi Macs?
6 What is your OSX version?

I apologize for the difficulties this issue causes and I really do want to get this resolved.

Please can any of you describe the circumstances when the client crashes? Your assistance will mean that i am able to give the most detail to our programmers to fix this.

Are you undocking or docking?
Do you have CQ enabled or ship spinning?
Is there heavy graphical load?
What are your graphics settings?
Are you all using ATi Macs?
What is your OSX version?

I apologize for the difficulties this issue causes and I really do want to get this resolved.

Please can any of you describe the circumstances when the client crashes? Your assistance will mean that i am able to give the most detail to our programmers to fix this.

Are you undocking or docking?
Do you have CQ enabled or ship spinning?
Is there heavy graphical load?
What are your graphics settings?
Are you all using ATi Macs?
What is your OSX version?

I apologize for the difficulties this issue causes and I really do want to get this resolved.

Please open /Users/Account Name/Library/Application\ Support/Eve Online/p_drive/

Attach "Win32 CrashReport" and "Win32_minidump.dmp" to a bug report and call it "For Konflikt : Mac Crash" or similar and I will endavour get this fixed as fast as i can :)

0004:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71058ae8 name="322 RtlCreateHeap() &NewHeap->CS" ec=191 cc=191
0004:err:ntdll:display_wait_error backtrace=(null)
0004:err:ntdll:display_wait_error crit (0x71058ae8): lc 261 rc 258 ot 7 sem 93759 spin 0
000c:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=3 cc=3
000c:err:ntdll:display_wait_error backtrace=(null)
000c:err:ntdll:display_wait_error crit (0x70137fe0): lc 3 rc 1 ot 4 sem 163355 spin 0
001d:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=3 cc=3
001d:err:ntdll:display_wait_error backtrace=(null)
001d:err:ntdll:display_wait_error crit (0x70137fe0): lc 3 rc 1 ot 4 sem 163355 spin 0
0016:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=3 cc=3
0016:err:ntdll:display_wait_error backtrace=(null)
0016:err:ntdll:display_wait_error crit (0x70137fe0): lc 3 rc 1 ot 4 sem 163355 spin 0
0021:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=4 cc=4
0021:err:ntdll:display_wait_error backtrace=(null)
0021:err:ntdll:display_wait_error crit (0x70137fe0): lc 4 rc 1 ot 4 sem 163355 spin 0
0004:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71058ae8 name="322 RtlCreateHeap() &NewHeap->CS" ec=193 cc=193
0004:err:ntdll:display_wait_error backtrace=(null)
0004:err:ntdll:display_wait_error crit (0x71058ae8): lc 262 rc 258 ot 7 sem 93759 spin 0
000c:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=7 cc=7
000c:err:ntdll:display_wait_error backtrace=(null)
000c:err:ntdll:display_wait_error crit (0x70137fe0): lc 4 rc 1 ot 4 sem 163355 spin 0
001d:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=7 cc=7
001d:err:ntdll:display_wait_error backtrace=(null)
001d:err:ntdll:display_wait_error crit (0x70137fe0): lc 4 rc 1 ot 4 sem 163355 spin 0
0016:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=7 cc=7
0016:err:ntdll:display_wait_error backtrace=(null)
0016:err:ntdll:display_wait_error crit (0x70137fe0): lc 4 rc 1 ot 4 sem 163355 spin 0
0021:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=8 cc=8
0021:err:ntdll:display_wait_error backtrace=(null)
0021:err:ntdll:display_wait_error crit (0x70137fe0): lc 4 rc 1 ot 4 sem 163355 spin 0
0004:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71058ae8 name="322 RtlCreateHeap() &NewHeap->CS" ec=194 cc=194
0004:err:ntdll:display_wait_error backtrace=(null)
0004:err:ntdll:display_wait_error crit (0x71058ae8): lc 262 rc 258 ot 7 sem 93759 spin 0
000c:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=11 cc=11
000c:err:ntdll:display_wait_error backtrace=(null)
000c:err:ntdll:display_wait_error crit (0x70137fe0): lc 4 rc 1 ot 4 sem 163355 spin 0
001d:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=11 cc=11
001d:err:ntdll:display_wait_error backtrace=(null)
001d:err:ntdll:display_wait_error crit (0x70137fe0): lc 4 rc 1 ot 4 sem 163355 spin 0
0016:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=11 cc=11
0016:err:ntdll:display_wait_error backtrace=(null)
0016:err:ntdll:display_wait_error crit (0x70137fe0): lc 4 rc 1 ot 4 sem 163355 spin 0
0021:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=12 cc=12
0021:err:ntdll:display_wait_error backtrace=(null)
0021:err:ntdll:display_wait_error crit (0x70137fe0): lc 4 rc 1 ot 4 sem 163355 spin 0
0004:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71058ae8 name="322 RtlCreateHeap() &NewHeap->CS" ec=195 cc=195
0004:err:ntdll:display_wait_error backtrace=(null)
0004:err:ntdll:display_wait_error crit (0x71058ae8): lc 262 rc 258 ot 7 sem 93759 spin 0
000c:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=15 cc=15
000c:err:ntdll:display_wait_error backtrace=(null)
000c:err:ntdll:display_wait_error crit (0x70137fe0): lc 4 rc 1 ot 4 sem 163355 spin 0
001d:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=15 cc=15
001d:err:ntdll:display_wait_error backtrace=(null)
001d:err:ntdll:display_wait_error crit (0x70137fe0): lc 4 rc 1 ot 4 sem 163355 spin 0
0016:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=15 cc=15
0016:err:ntdll:display_wait_error backtrace=(null)
0016:err:ntdll:display_wait_error crit (0x70137fe0): lc 4 rc 1 ot 4 sem 163355 spin 0
0021:err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=16 cc=16
0021:err:ntdll:display_wait_error backtrace=(null)
0

I understand where crash dumps are, but the way the client is freezing, doesn't write anything to that file. It just goes "Poof"

I know that doesn't help you, but it also doesn't help us :)

I also know how to run the client with logging turn on, but i haven't run the game in that manner in a while (Feb 17 to be exact.) I will try and run it like that from now on to hopefully get something for you.

BTW: Do you know how to run multiples from the cider trace log instructions? I typically run up to 10 clients and can never get anything more than 1 to open using cider trace log thing. Or is that not really an option anymore with the built in logging?

Please can any of you describe the circumstances when the client crashes? Your assistance will mean that i am able to give the most detail to our programmers to fix this.

Are you undocking or docking?
Do you have CQ enabled or ship spinning?
Is there heavy graphical load?
What are your graphics settings?
Are you all using ATi Macs?
What is your OSX version?

I apologize for the difficulties this issue causes and I really do want to get this resolved.

I have now been up and down these folders, and there are no dump files there after the crash. i only have a stack of folders an no files in that folder

All UsersLocal SettingsSendTo
Application DataMy DocumentsStart Menu
CookiesNetHoodTemplates
DesktopPrintHood
FavoritesRecent

i did however get this from GM Haggis

http://wiki.eveonline.com/en/wiki/Mac_Bug_Reporting#Generating_Log_Files

Is you use this you generate a log file using this method:


Launch Terminal. You can find Terminal using Spotlight; it can also be located in "/Applications/Utilities"
Right click on the EVE install that you wish to redirect, and select 'Show Package Contents'
Open the 'Contents' folder, then the 'MacOS' folder
Drag the 'cider' file into the Terminal window, this will generate a link directly to the cider file. USER$ /Applications/EVE/EVE.app/Contents/MacOS/cider (this may look different if you renamed the EVE application, don't worry!)
Add the following to the end after .../cider ' -debugmsg +seh,+tid,+module,+debugstr &> ~/Desktop/EVEcrashlog.log'. Note the space.
The command should now look like; 'USER$ /Applications/EVE/EVE.app/Contents/MacOS/cider -debugmsg +seh,+tid,+module,+debugstr &> ~/Desktop/EVEcrashlog.log'
Hit ENTER to execute the command. This will start logging and generate the logs to the Desktop in a file called "EVEcrashlog.log"
Once the bug has been reproduced, ZIP the EVEcrashlog.log file and upload the zipped copy to the bug report.

i have submitted that to Support, but no answer so far.

Nope, no memory references (or debug windows whatsoever). Just hard locks of the application with stuttering sounds.

I can try to get it to coredump later tonight if that helps, I think a ^\ should do that. I'm not absolutely sure if that's helpful when it's wrapped in cider or wine, but can't do any harm I guess.

I did get a crash just now infact, this crash presents the debug option as described.

It's pointing to 0x00000000 which is not so healthy.

Do you all get a memory reference like this or different?

This one will be fixed very soon.

I'm not sure this is relevant but....

I haven't crashed, frozen or disconnected for 2 days now (and I froze like 5-10 times a day before).

What changed? I guess it could be something CCP did, but I also recalled I did something else about 2 days ago:

I went here and followed the instructions: http://www.eveonline.com/ingameboard.asp?a=topic&threadID=1021336

I'm not saying this necessarily made my client stable, but it is a rather curious coincidence, right?

AP

Started locking up on me today. Worked fine until server restart on 8th Dec. Mac OS 10.6.8 on MacBook Pro.

A few seconds after I login the client freezes up, as if I've been disconnected. But yet I can still see other people chatting away.

:: edit ::
This is definitely something to do with the server, because my other account that runs on a Win7 machine is now also crashing. I've never experienced any crashes until today on either machines.

And it forces me into a hard reboot...

Try Command+Option+Esc, Mac OS should kill your foremost application if in fullscreen or bring up the Force Quit Applications window otherwise.

Or your internet connection

Every time one actively tries to crash an application it somehow refuses. Heisenbugs are literally the worst bugs :(. Currently running eve with output of cider tee'd into a textfile. When it crashes I'll update this post with pastebins of the cider output and a coredump (if it yields one).

/Applications > cd EVE\ Online.app/Contents/MacOS
/Applications/EVE Online.app/Contents/MacOS > ./cider 2>&1 | tee ~/cideroutput.txt
fixme:win32:PE_CreateModule Security directory ignored
fixme:win32:PE_CreateModule Load Configuration directory ignored

fixme:ddraw:MapSamplerIndex unsupported texture stage/sampler 19
err:heap:RtlFreeHeap block 0x4346b390 isn't a valid part of heap 0x71824df0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71824e18 name="322 RtlCreateHeap() &NewHeap->CS" ec=760 cc=760
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71824e18): lc 274 rc 270 ot 5 sem 87139 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71824e18 name="322 RtlCreateHeap() &NewHeap->CS" ec=760 cc=760
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71824e18): lc 274 rc 270 ot 5 sem 87139 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71824e18 name="322 RtlCreateHeap() &NewHeap->CS" ec=760 cc=760
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71824e18): lc 274 rc 270 ot 5 sem 87139 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71824e18 name="322 RtlCreateHeap() &NewHeap->CS" ec=760 cc=760
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71824e18): lc 274 rc 270 ot 5 sem 87139 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71824e18 name="322 RtlCreateHeap() &NewHeap->CS" ec=760 cc=760
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71824e18): lc 274 rc 270 ot 5 sem 87139 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71824e18 name="322 RtlCreateHeap() &NewHeap->CS" ec=761 cc=761
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71824e18): lc 275 rc 270 ot 5 sem 87139 spin 0

err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71846398 name="322 RtlCreateHeap() &NewHeap->CS" ec=5019 cc=5019
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71846398): lc 5 rc 1 ot 12 sem 50691 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71846398 name="322 RtlCreateHeap() &NewHeap->CS" ec=5019 cc=5019
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71846398): lc 5 rc 1 ot 12 sem 50691 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71846398 name="322 RtlCreateHeap() &NewHeap->CS" ec=5019 cc=5019
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71846398): lc 5 rc 1 ot 12 sem 50691 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71846398 name="322 RtlCreateHeap() &NewHeap->CS" ec=5019 cc=5019
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71846398): lc 5 rc 1 ot 12 sem 50691 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71846398 name="322 RtlCreateHeap() &NewHeap->CS" ec=5019 cc=5019
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71846398): lc 5 rc 1 ot 12 sem 50691 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71846398 name="322 RtlCreateHeap() &NewHeap->CS" ec=5021 cc=5021
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71846398): lc 7 rc 1 ot 12 sem 50691 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71846398 name="322 RtlCreateHeap() &NewHeap->CS" ec=5021 cc=5021
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71846398): lc 7 rc 1 ot 12 sem 50691 spin 0
^C

fixme:ddraw:MapSamplerIndex unsupported texture stage/sampler 16
fixme:ddraw:MapSamplerIndex unsupported texture stage/sampler 17
fixme:ddraw:MapSamplerIndex unsupported texture stage/sampler 18
fixme:ddraw:MapSamplerIndex unsupported texture stage/sampler 19

err:heap:RtlFreeHeap block 0x3f2f8e68 isn't a valid part of heap 0x71085920
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71085948 name="322 RtlCreateHeap() &NewHeap->CS" ec=153 cc=153
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71085948): lc 6 rc 1 ot 12 sem 97031 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71085948 name="322 RtlCreateHeap() &NewHeap->CS" ec=153 cc=153
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71085948): lc 6 rc 1 ot 12 sem 97031 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71085948 name="322 RtlCreateHeap() &NewHeap->CS" ec=153 cc=153
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71085948): lc 6 rc 1 ot 12 sem 97031 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71085948 name="322 RtlCreateHeap() &NewHeap->CS" ec=153 cc=153
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71085948): lc 6 rc 1 ot 12 sem 97031 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71085948 name="322 RtlCreateHeap() &NewHeap->CS" ec=153 cc=153
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71085948): lc 6 rc 1 ot 12 sem 97031 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x71085948 name="322 RtlCreateHeap() &NewHeap->CS" ec=153 cc=153
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x71085948): lc 6 rc 1 ot 12 sem 97031 spin 0
^C

err:heap:RtlFreeHeap block 0x3ba98770 isn't a valid part of heap 0x70545ff0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=6 cc=6
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x70137fe0): lc 37 rc 32 ot 7 sem 141059 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=6 cc=6
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x70137fe0): lc 37 rc 32 ot 7 sem 141059 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=6 cc=6
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x70137fe0): lc 37 rc 32 ot 7 sem 141059 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=6 cc=6
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x70137fe0): lc 37 rc 32 ot 7 sem 141059 spin 0
err:ntdll:display_wait_error Timeout. Retry with 60 secs: crit=0x70137fe0 name="The CriticalSection CriticalSection" ec=6 cc=6
err:ntdll:display_wait_error backtrace=(null)
err:ntdll:display_wait_error crit (0x70137fe0): lc 37 rc 32 ot 7 sem 141059 spin 0
^C

Here is my sad story:
http://eve-kill.net/?a=kill_detail&kll_id=11864657
http://eve-kill.net/?a=kill_detail&kll_id=11864670
THX for stable client....

eh..?

I cannot believe CCP did nothing about this? All the while official web page has a downloadable MAC Client

I want a statement that CCP keeps supporting MAC and I want it before the coming seasonal holidays

Yeah. Leave. Theres so many great new games out there.

Btw what do you mean well earned when I cannot even play the hole thing?

Oddly enough, the client I run for my empire toon has yet to have *any* problems. Only the one I use for my main has frozen.

For months before that, the Devs had been taking the brunt of the heat for Hillmar's decisions. So they could probably use a break about now.

[...] the client I run for my empire toon [...] Only the one I use for my main has frozen.

You got that right.

What do you mean by Empire Toon Client?

Dualboxing? Are we all doing that?

My impression is it sure crashes often when dualboxing and less so when playing one client only. Though not sure of my judgment there because I dualbox all the time. Or maybe after I 'clean installed' Crucible I flew round to awe the new nebulae in different regions. So many jumps to see different kinds of stations and stargates in the new environment as well as the new nature of nebula reflection on my ship. Everything in Crucible working real smoothly - video performance brilliant and seamless as in MAC style, indicating no reasons for worry. Then 'copy as EVE2' and do the 'plist thing' and run my logi pilot account and soon find either or both clients crashing constantly.

Crash this evening when undocking.

"Unhandled page fault on read access to 0x00000039 at address 0x71cf71d5"

2.66GHz Intel Core i7

/Applications % rm -rf EVE\ Online.app/

~/Library/Application Support % rm -rf EVE\ Online

I can forgive this. Of course I can. But really guys, there IS a clock here, and what happens when the second month goes by, and someone decides that hey, we had an agreement involving what I could play this on.
At this point, a month on, the bridge crew needs to get involved and the red shirts need to start piling into the transporter room.

I understand problems. I don't understand ignoring a customer.

Not empty quoting.

strat...doesn't that generally indicate a memory leak?
I'm not an expert in syntactic tech, but I've been told that for similar situations.

Anyways, day 34!

I lowered my graphics settings. No CTD for 24 hours.

I've had this problem since patch as well. I've tried three (!) different Macbook Pro's and I can, after over a month of client freezes (= force quit every single freeze) say that it happens more on the Macbook Pro that had 4GB instead of 8GBs which the other two had.

And, not to be whiny but, it's hard to be any useful in fleets and paying the monthly fee just to keep the skill training going is quite irritating.

Day 37.

Maybe someone needs to head over to the fanfest, get on the mic and ask the big question on behalf of their mac brothers and sisters?

The question being: "What's going on with the mac service outage? a month is a long time..."

Odd thing, on my macbook it works "fine", without crashing. It has less memory though, and a worse videocard. But because the hardware is so much less powerful it's a total pain to play on.

Feels like video card specific, different video cards seem to give different results.

However, I've discovered that I get fewer crashes the less memory I use, meaning closing a lot of applications before starting EVE helps, but it does not guarantee a crash safe gaming session.

........

Is there a third option, anyone?

And with all the feedback and updates people in the main PC issues thread get at this point I'm starting to think we Mac users need to start shooting the Jitta monument.

No logs? Managed to produce logs by using descriptions earlier in this thread. However, I have no clue about what to do with them.

I'm going o open a petition now and I will not give up.

Wish me luck.

day 41. Really?

After some more trying it seems to be easy to force a freeze at least on my computer.
If I run out of free memory due to inactive memory taking up too much space eve will freeze and will need to be force quitted.

How do you get inactive memory to take up too much space?

And ..doing other network activities while eve is up???? That tempting fate, tickling the dragon's tail, and asking for it all at once. If you are having issues, kill ALL other activities other than eve.

well there goes my hypothesis out the window...anyone care to make an educated guess?

Because it's looking like we may have to wait until the next expansion to play eve again...

edit: quote box isn't working for some reason. Just imagine it, k?

Sorreee

I was in windowed keeping an eye on the ram and CPU via iStat menus.

One thing I did notice though is that when it 'locks up', it's still using CPU cycles in Activity Monitor.

I'm beginning to wonder if it's a graphical issue via the transgaming emulator converting the Direct X? Maybe there's something bugging it and it just stops rendering the graphics?

Hello, and welcome to day 50 of the mac service outage.

To recap: There has been confirmation of work being done on the problem by that Konflikt guy, but so far nothing has been mentioned about recouping the time lost during the outage.
Personally, I would be satisfied with having the lost time appended to the end of my subscription.

Perhaps I should open a petition?

Still crashing every 10 minutes or so...
I assume holidays should be over by now. Can we get an update on the situation? Were mac devs layed off and mac client will be discontinued in the next few months?
Should we get PCs if we want to continue playing EVE?

Do you use bootcamp or some sort of inline emulator?

Sad thing is i'm one of a small minority that has raid card setup, and bootcamp is not supported on my machine.
I'm pretty sure after two months majority of mac users moved on to bootcamp, and those like me will be left behind when mac client will be finally discontinued :(

I mean.. we got used to playing with minimal settings without sound on high-end machines. We adjusted to more lag during fights, overheating and setting up preferences every other week, not using probes and learning to work around the behavior that crashes the client. But this, where you get freezes randomly no matter what you were doing, in most random places as often as few minutes really pushes it over the edge..

If you have trouble identifying or replicating issues, i'm (as im sure many here) are ready to give you our time and cooperation, to help fix it. Just please, please do something about it.

Please do! I'd really appreciate that :)

Just ran a dozen missions with no crashes to report...did something quietly get fixed at some point?

Thanks for that Parallels guide. Absolutely amazing that we can emulate windows and run the client perfectly, but we can't emulate the client. -.-

Maybe you guys should drop Transgaming and get Parallels to work on the emulation, they clearly know what they are doing.

Thanks for that Parallels guide. Absolutely amazing that we can emulate windows and run the client perfectly, but we can't emulate the client. -.-

Maybe you guys should drop Transgaming and get Parallels to work on the emulation, they clearly know what they are doing.

Day two of regular/heavy play and only two crashes, which is more or less normal. Seriously, what changed?

It certainly wasn't my system.

Hopeless... froze in the first pocket of the first mission I tried to run...

Something's changed but not everyone is benefiting.

Please can any of you describe the circumstances when the client crashes? Your assistance will mean that i am able to give the most detail to our programmers to fix this.

Are you undocking or docking?
Do you have CQ enabled or ship spinning?
Is there heavy graphical load?
What are your graphics settings?
Are you all using ATi Macs?
What is your OSX version?

I apologize for the difficulties this issue causes and I really do want to get this resolved.

So the latest string of patches haven't fixed a thing. I don't know how many days it has been, but this is utterly ridiculous.

So I started seeing crashes when I had uTorrent running in the background.
This got me thinking: what would change without announcement, and get...confused...by a program sharing bandwidth?

The anti-cheating program. You see, warcrack had this problem a long time ago, where their super creepy "warden" program (which is also a data-miner if you didn't know...it reads everything on your desktop, anything running and sends it back to actiblizz;
who, due to the TOS players sign, own all that data. That book you're typing up while playing? they own it now.) kept halting warcrack when certain programs were running, or even getting confused and clogging the system like a massive turd.

Thoughts?

Wow, this patch killed my client!!! I logged on before dt, no problem. Logged off, applied new patch after dt. Black screen followed.

I have found a temp fix tho. If i make a clone of my client, the clone works.

Hope this help someone. Cause CCP are doing **** all.

Interesting, since patch markets and contracts no longer work in my main client however, a clone made with clonemaker has no such issues. It just crashes randomly.

So i reinstalled the game one and still having the problem basically i click on the Eve Online Icon it starts up EVE ONLINE CRICIBLE POPS up and then goes away right after that nothing happens and then my mac lags out and i have to force quit then game!!!!!
for 2 days now

im losing skill training by them second
Processor: 2.8 GHz Intel Core 2 Duo
Memory : 4 GB 1067 MHz DDR3
Graphics: NVIDIA GeForce 9600M GT 512 MB
Software: Mac OS X Lion 10.7.2 (11C74)

Just canceled another account. The game is currently unplayable on my mac. Constantly locking up. In stations, jumping through gates, running missions, everything. Have submitted a bug report. I've already tried deleting the preferences and clearing various caches. Nothing has worked.

This is my last account. If the mac client doesn't start receive more development, than I'll have to cancel this one as well. Just not worth it. Also, the lack of communication from CCP and any sort of hint as to what the future of the mac platform might hold is extremely frustrating. It would be nice if CCP would tell the mac crowd if we can expect any improvements and added resources to the development of the mac client.

I fully support these words certainly understand that CCP is not so much to lose if the owners of the MAC OS will no longer play because of technical problems. But the mere fact that they ignore the problem of users, will prove to everyone how much they respected the users, and how much care about the game.

how about instead of crying and posting into the crash thread instantly to voice your frustration, you look at the forums and look for the fix thread?

Here it is for you if you are too lazy/blind to do so

Good, you could do the same and read the thread to notice that some of us have said that several times already, others have done that several times and the problems are still there...

**sigh**

how about instead of crying and posting into the crash thread instantly to voice your frustration, you look at the forums and look for the fix thread?

Here it is for you if you are too lazy/blind to do so

I don't know if it has been fixed yet, to be honest I lost all hope. I do know that Apple once had Eve Online screenshots and links when they talked about games on their websites or publications. I can't find any reference to Eve Online at all anymore.

I guess Apple themselves got fed up with CCP as well.

Sony will be next I'm betting ..... seems like CCP can not handle cross platform support ....... I was planning on getting a PS3 to play Dust ..... not a chance of that happening now. CCP Mac users do talk with PC users you might want to ignore us because we are the minority but ineptitude at cross platform support will negatively impact migration of EVE Online players to Dust. Seriously how can we have any confidence in your technical ability to link our computers to the same universe with a game console when you can't keep Mac and PC systems working at the same time?