Game crashes whenever I enter a portal, try to use a shrine, or try to enter a dungeon or a quest

Federico · May 2014

Hi,

I've seen multiple threads on issues similar to these. I'm using a macbook pro retina displaym turned all the graphics to minimum resolution, tried repairing the client, but the error keeps happening...it's so frustrating! please help?

Moonraker · May 2014

Federico wrote: »

Hi,

I've seen multiple threads on issues similar to these. I'm using a macbook pro retina displaym turned all the graphics to minimum resolution, tried repairing the client, but the error keeps happening...it's so frustrating! please help?

Hi, can you confirm exactly what error message it shows? Is this all the time, or after a period of play. Is it at quieter time as well as peak times on server?

Can you post system details will help to get a better idea;

Apple icon (top left of menu bar) > About This Mac > More info…

If you are close to memory limit then loading in the new data for the new location could bring it over the limit and crash. Or, it could be server related too.

If you get a ZOSCrashReporter summary before submitting copy and paste here (use Spoiler tags which can be found under Quote on the post editor looks like a backwards P) which should help to tell if it's memory issue or something else.

Saparok · May 2014

Since 1.07, the ZOS crash reporter no longer catches fatal exceptions from the Mac Client for me. Instead, the Apple crash reporter catches them, and sends them off to Apple instead. I've submitted an in-game bug report on that by the way.

The crashes as caught by the Apple utility say "bad_alloc". I'm guessing memory leak, despite it supposedly being addressed in a prior patch, not that anyone wants my guess. The main difference is that the ZOS tool no longer seems able to catch these errors, but it did previously.

It typically happens after 1-2 hours of in-game time. However, zoning in/out of instances seems to make it happen more often.

Just now I was downloading another patch from the loader. However, the posts on this site still say 1.07 is the latest, so I'm not really sure what I just patched in.

Perhaps this is a Mac only patch, and didn't make the general patch notes? Launching it just now after the patch was applied, it reads Version: eso.live.1.0.7.980598 on the login screen.

Btw, I'm running on 10.9.2 of OS X, with a dual quad-core Mac Pro with 10GB of RAM.

Moonraker · May 2014

The general problems you describe is the memory issue (Apple crash report shows that)

Like I said, using a way shrine or loading a new location is most likely just taking it over the 4GB 32-bit limit (bit lower in practice)

The patch updated today in NA (Europe tomorrow) is 1.0.7 with Patch Notes here. The previous patch 1.0.6 from last week had some Mac notes in it.

It's a little hard as the dual CPU Macs are no officially supported, though some do anyhow or with the workaround so it's hard to say it there is anything else effecting this.

Generally if you set the graphics appropriate to the Mac graphics card it should give 3-4 hours between crashes although highly populated towns etc. will reduce this.

Try setting the Texture Quality to Medium (or Low as appropriate) should help extend the time between crashes.

the developers are continuing to release fixes for any memory leaks they find and to address any others they find.

Saparok · May 2014

Moonraker wrote: »

Like I said, using a way shrine or loading a new location is most likely just taking it over the 4GB 32-bit limit (bit lower in practice)

To be clear, is the client 32-bit only? This is running on a 64-bit system, with 2.5X more memory than 4GB.

Lines that involve a lot of loading screens (like those "kill some bad dudes in somebody else's dream sequence") seem to really make this show up. Quite often you will crash straight out of the game when it tries to return you to the normal zone.

Moonraker · May 2014

Saparok wrote: »

Moonraker wrote: »

Like I said, using a way shrine or loading a new location is most likely just taking it over the 4GB 32-bit limit (bit lower in practice)

To be clear, is the client 32-bit only? This is running on a 64-bit system, with 2.5X more memory than 4GB.

Lines that involve a lot of loading screens (like those "kill some bad dudes in somebody else's dream sequence") seem to really make this show up. Quite often you will crash straight out of the game when it tries to return you to the normal zone.

Yep. The Mac & PC clients are 32-bit processes. Hence the 4GB limit. 64-bit client is planned at some point.

Saparok · May 2014

Here is an abbreviated (it goes on for pages) crash report like are being sent to apple when the client crashes.

Process: eso [5618]
Path: /Applications/Zenimax Online/Launcher.app/game_mac/pubplayerclient/eso.app/Contents/MacOS/eso
Identifier: com.zenimaxonline.eso
Version: 1.0.0 (1.0.0)
Code Type: X86 (Native)
Parent Process: ZeniMax Online Studios Launcher [5613]
Responsible: ZeniMax Online Studios Launcher [5613]
User ID: 502

Date/Time: 2014-05-05 17:11:30.402 -0500
OS Version: Mac OS X 10.9.2 (13C64)

Crashed Thread: 8

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
abort() called

Thread 8 Crashed:
0 libsystem_kernel.dylib 0x9ac68952 __pthread_kill + 10
1 libsystem_pthread.dylib 0x92a7a167 pthread_kill + 101
2 libsystem_c.dylib 0x91b7829c abort + 155
3 libc++abi.dylib 0x97edc6c9 abort_message + 169
4 libc++abi.dylib 0x97efd47d default_terminate_handler() + 264
5 libc++abi.dylib 0x97efac30 std::__terminate(void (*)()) + 14
6 libc++abi.dylib 0x97efa64b __cxa_throw + 116
7 libc++abi.dylib 0x97efae74 operator new(unsigned long) + 100
8 com.zenimaxonline.eso 0x0001cac3 start + 107011
9 com.zenimaxonline.eso 0x01806923 wcsncasecmp + 11272947
10 com.zenimaxonline.eso 0x01804c32 wcsncasecmp + 11265538
11 com.zenimaxonline.eso 0x016e5e2a wcsncasecmp + 10090490
12 com.zenimaxonline.eso 0x016e9fb4 wcsncasecmp + 10107268
13 com.zenimaxonline.eso 0x016f1359 wcsncasecmp + 10136873
14 com.zenimaxonline.eso 0x016eeb9a wcsncasecmp + 10126698
15 com.zenimaxonline.eso 0x016ee518 wcsncasecmp + 10125032
16 com.zenimaxonline.eso 0x016ee48c wcsncasecmp + 10124892
17 com.zenimaxonline.eso 0x00dbdd97 wcsncasecmp + 489319
18 com.zenimaxonline.eso 0x00dbdc97 wcsncasecmp + 489063
19 com.zenimaxonline.eso 0x00d4d18a wcsncasecmp + 27482
20 com.zenimaxonline.eso 0x00d4dfc5 wcsncasecmp + 31125
21 com.zenimaxonline.eso 0x00d4ddea wcsncasecmp + 30650
22 com.zenimaxonline.eso 0x0181623b wcsncasecmp + 11336715
23 com.zenimaxonline.eso 0x01816cf0 wcsncasecmp + 11339456
24 com.zenimaxonline.eso 0x00042fe0 start + 263968
25 com.zenimaxonline.eso 0x01818d16 wcsncasecmp + 11347686
26 com.zenimaxonline.eso 0x018193c4 wcsncasecmp + 11349396
27 libsystem_pthread.dylib 0x92a795fb _pthread_body + 144
28 libsystem_pthread.dylib 0x92a79485 _pthread_start + 130
29 libsystem_pthread.dylib 0x92a7ecf2 thread_start + 34

Thread 8 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0xa05d7c0c ecx: 0xb05a57bc edx: 0x9ac68952
edi: 0xb05a7000 esi: 0x00000006 ebp: 0xb05a57d8 esp: 0xb05a57bc
ss: 0x00000023 efl: 0x00000206 eip: 0x9ac68952 cs: 0x0000000b
ds: 0x00000023 es: 0x00000023 fs: 0x00000023 gs: 0x0000000f
cr2: 0xa05d6d00

Logical CPU: 0
Error Code: 0x00080148
Trap Number: 132

VM Region Summary:
ReadOnly portion of Libraries: Total=334.5M resident=84.8M(25%) swapped_out_or_unallocated=249.8M(75%)
Writable regions: Total=3.2G written=931.8M(28%) resident=2.7G(84%) swapped_out=369.1M(11%) unallocated=536.4M(16%)

REGION TYPE VIRTUAL
=========== =======
CG backing stores 22.6M
CG image 12K
CG raster data 92K
CG shared images 204K
IOKit 173.1M
Kernel Alloc Once 4K
MALLOC 1.6G
MALLOC (admin) 48K
Memory Tag 242 12K
Stack 78.5M
VM_ALLOCATE 1.5G
__DATA 24.1M
__IMAGE 528K
__IMPORT 16K
__LINKEDIT 93.4M
__OBJC 3920K
__PAGEZERO 4K
__TEXT 241.2M
__TEXT0 2220K
__UNICODE 544K
mapped file 88.4M
shared memory 68K
=========== =======
TOTAL 3.7G

Moonraker · May 2014

Saparok wrote: »

Here is an abbreviated (it goes on for pages) crash report like are being sent to apple when the client crashes.

---snip--
Application Specific Information:
terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
abort() called

Yep, memory crash. All Apple reports are the same so far.

NeKryXe · November 2015

that's weird. i'm using a PC with win7 and i'm not able to enter dungeons anymore. it always crashes.

in 2014, before the game was free to play i was able to enter any dungeon, but now it doesn't work any more.
it seems that it is no longer an apple problem.