It will also open the ZOSCrashReporter for memory crashes also. Just when it fails to do so you get the Apple log showing it instead.thatlaurachick wrote: »And just got a crash - but it's not the memory leak bug (because the ZOS crash reporter actually popped up). Just because the memory leak bug was fixed doesn't mean the client won't crash at all. It was supposed to crash less...
if you look at the reports (here or own) at:
mem.current = xxxx
xxxx for memory crash will typically when it reaches 2700+. Perhaps a little more now since the small memory leaks. Sometimes it shows an erroneous value but mostly it at least gives a decent indication.
You can view memory at time of crash also via Activity Monitor > Memory and double click the eso process to open the window to show Real Memory and Virtual Memory. This way you can also reboot the game when it gets close to avoid the crash.
It's shows the resident value (2.8GB in this example)VM Region Summary:
ReadOnly portion of Libraries: Total=345.1M resident=133.5M(39%) swapped_out_or_unallocated=211.6M(61%)
Writable regions: Total=3.1G written=1.1G(35%) resident=2.8G(90%) swapped_out=0K(0%) unallocated=316.1M(10%)
REGION TYPE VIRTUAL
=========== =======
CG backing stores 14.0M
CG image 28K
CG raster data 112K
CG shared images 204K
IOKit 670.8M
IOKit (reserved) 4K reserved VM address space (unallocated)
Kernel Alloc Once 4K
MALLOC 1.5G
MALLOC (admin) 48K
Memory Tag 242 12K
Stack 74.9M
VM_ALLOCATE 912.7M
__DATA 37.0M
__IMAGE 528K
__IMPORT 4K
__LINKEDIT 93.4M
__OBJC 3884K
__PAGEZERO 4K
__TEXT 251.6M
__TEXT0 2224K
__UNICODE 544K
mapped file 82.9M
shared memory 68K
=========== =======
TOTAL 3.6G
TOTAL, minus reserved VM space 3.6G
Ragnar_Lodbrok wrote: »Templars do more dps than DK's.
Answered you in the other thread you started to explain this more.500mbit down/sec 100mbit/sec up internet COMHEM (Sweden, Stockholm)
3,5 GHz Intel Core i7
32 GB 1600 MHz DDR3
NVIDIA GeForce GTX 780M 4096 MB
OS X 10.9.2
It doesn't matter what I'm doing. I keep crashing whether standing still near a WP, doing dungeons, crafting, you name it. Immensley long loading screens.
ALSO PUT SERVERS IN EU ALREADY
Not sure where it will indicate OpenGL errors? If you can post crash summary or source of that errorThe mac client crashes are superbly annoying.
The only errors I get are OpenGL errors.
Most likely the memory issue which is well documented here in the Mac Technical Support section. It is noted as a known issue here in the Known Technical Issues (Mac) sticky above.christopher.pesapaneub17_ESO wrote: »Does eso cause anyone else's Mac to crash back to the Mac profile login? This happens once or twice a day to me along with the numerous game crashes that pull up the crash reporter. I'm not sure if there is a fix for this but the game is pretty hard to play if its crashing in the middle of a dungeon or upon turning in a quest that you have to repeat once you log back in.
As has been posted extensively in this section and included in the Known Technical Issues (Mac) there is a memory issue in the Mac client which causes crashing over time. In PVE questing it is between 2-4 hours (depends on time in busy towns) and more frequently in PvP, typically 20-40 minutes in big battles.I have same problem, client crash every 10 minutes in RvR, i have iMac last version 8 GB ram.... what i can do for fix this?
Crashing every 10 minutes indicates other issues which do exist notably in Cyrodiil which are server-side.
I have the same experience mostly due to me spending most of my time on forums for the first two weeks soStrongblade wrote: »From my experience virtually all the bugged quests seem to be fixed. Haven't encountered a bugged quest in a while. Really just the Mac Memory crash that I encounter anymore. Otherwise most of the other stuff has been fixed.
So really, the fix will probably be the release of a 64-bit client.