The ESO crash reporter sends us a proper crash dump when you hit the send button.
So I have been playing this game since open beta around a year ago. During open beta I have reported lots of times that the mac client crashes in pvp (approximately every 5 min). When game went live I was hoping that this issue was fixed. NO it wasn't, game still crashed every 5 min in pvp. I thought that maybe additional patches over the year will fix it, well they didn't. After playing eso for more than 11 month I still have this issue on mac. I cannot pvp on the mac client EVER, as I periodically crash every 5-10 min. I have top of the line iMac btw. THE ONLY SOLUTION TO THIS CRASH ISSUE IS TO INSTALL WINDOWS ON YOUR MAC AND RUN A WINDOWS CLIENT. In windows I never crash, I can pvp for days and it will be fine. I am sorry to say this but the mac client is garbage, not only does it crash really often, the frame rates are typically 1.5-2 times less than what is in windows on the same graphics quality on the same freaking computer.
We are very happy things are working better. We can see from our crash reports that up times are well up, including PvP now averaging around 2-3 hours versus 10 minutes, etc.
Thing is the patch notes don't even hint they've made any changes, so ... why thank them for seemingly doing nothing?Wow, that's great news, Chris. Thanks for the update, and thanks for the fixes!
http://forums.elderscrollsonline.com/en/discussion/163301/patch-notes-v2-0-4but they've published no information to make us think anything got changed!
- We have added memory optimizations to help the game client from exceeding available memory.
We are very happy things are working better. We can see from our crash reports that up times are well up, including PvP now averaging around 2-3 hours versus 10 minutes, etc.Thing is the patch notes don't even hint they've made any changes, so ... why thank them for seemingly doing nothing?Wow, that's great news, Chris. Thanks for the update, and thanks for the fixes!
Their figures may show improvement .. we have no way to verify that of course .. but they've published no information to make us think anything got changed!
This would be consistent with some older, more detailed crash reports (of exceptions caught by the OS, not the ZeniMax CrashReporter) I still have lying around; unfortunately, not every abort() is handled by the OS, and I keep even fewer of them. But besides errors like "std::bad_alloc", there are some "double free" errors. I also once got a "non-aligned pointer being freed", indicating trouble with memory management. But that's old news...Worst case scenario: You are trying to write to a memory location that you had reserved before, which however was in the meantime (as considered still old by some other part of you code due to a timing glitch) freed up (again).
terminating with uncaught exception of type std::bad_alloc: std::bad_allocor lately also of type
terminating with uncaught exception of type CryptoPP::OS_RNG_Err: OS_Rng: open /dev/urandom operation failed with error 24However, these seem all to be related to the live client, not the one for the PTS...