Nope. The ZOSCrashReporter does not leave a log. I just copy/ paste them to Notes.had a crash after the patch. about 2.5 hours in. accidently hit esc when the box popped up but had activity monitor up. Is there anyway to view the previous zos crash reports? I check in documents but no actual logs in the logs folder.
real mem 2.74gb
virt 3.89gb
shared 46.6mb
private 1.34gb
edit: fixed the time. CPU time was 2:25:14.60
Still crashing between 1-2 hours here. lets hope this actually fixes the issue.
Version = eso.live.1.0.5.972475
Yep as @KhajitFurTrader noted although you are on the NA server:KhajitFurTrader wrote: »
It doesn't say the issue. It probably could have been worked a bit differently but the general point is made, that work is ongoing to address the memory issue.Fixed an issue that would cause a gradual memory leak during long play sessions.
[reporter] version = 0.01 [extra] ProductName = eso Version = eso.live.1.0.6.976502 char.account = xxxxx char.alliance = 1 char.name = xxxx client.executablebits = 32 client.mode = inworld client.renderertype = OPENGL client.session_start_timestamp = 2014-05-01T19:44:20.819Z client.time_since_load = 1191 client.uptime = 1297.8 computer.name = localhost computer.user = xxxxxxx cpu.count = 4 data.depotid = 4001 data.dir = /Applications/ZeniMax Online/The Elder Scrolls Online EU/game_m data.syncm = databuild data.version = 0.win.0.live.976502 exe.buildnum = 976502 exe.opt = release exe.reltype = public exe.type = client gfx.description = AMD Radeon HD 6770M OpenGL Engine gfx.deviceid = 0.0.0 gfx.driver = 2.1 ATI-1.20.11 gfx.vendorid = 0 globby.address = 198.20.200.192 globby.port = 24506 loc.wloc = 43 498638 20635 677588 250.10 loc.world = Cyrodiil loc.worldid = 43 loc.zone = Cyrodiil login.address = 198.20.200.192 mem.current = 2544 mem.peak = 2742 mem.physical = 8192 os.platform = mac os.version = 13C64 realm.depotid = 0 realm.id = 4001 realm.name = EU Megaserver reportfield.ver = 3
Just to clarify, you copy/pasted the Apple crash report into your post. These are really long and will get cut off as they exceed the maximum post length.Rhynchelma wrote: »As I said, the crash took out the crash reporter too. As for "spamming" the forum, well, I don't know about the technicalities of the forum, this problem was supposed to have been fixed but is now worse and there's nothing chopped off about the console reports.
Application Specific Information:
terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
abort() called
Yep it is around 2.7GB Real Memory & 3.7GB Virtual Memory. In fact, as your image shows, it seems to be creeping upward which probably reflects some of the memory leak fixes to have already gone in.fried_funk wrote: »Just my 2 cents on this only to add to what others have already told, crash seems to happen when Virtual Memory nears 4GB limit
Crashed for some other reason as memory hardly used. Crash at launch?Glenumbra after hitting V1
I can see the client uptime is just over 59 minutes. Not sure where you tell the CPU time?Still crash pretty often, so figured Id post a new crash report here. normally its closer to 2hours with just PVE questing, but today its been about every hour.
Real mem 2.75GB, Virt 3.92GB, Shared 36.9MB, private 1.57GB
Something kind of odd that I haven't compared before... CPU time is 1:16:05.36 , client uptime is ~.99hr Wonder what the discrepancy is
Are we still in Beta?
Mac client is just a disaster for pvp… last patch doesn't fix anything.
Does Mac players have to install windows on Bootcamp for playing Teso?
Near 5K views, 180 comments and no official communication on Mac client…
Let us play with this jewell