That is the Apple crash report and can also be helpful as they do not get auto forwarded to ZOS.voxtor_turak wrote: »Another one:
- Arriving at the desert, at the shrine
THIS IS A NEW ERROR... has never seen this before... (at least, some good I suppose?)
---snip---
It's easier to deal with them then as they are very long and even the Spoiler tags cut them half way. Thanks.If you are getting proper CTD then is should generate an crash report and contains an crash text in it which would be useful to see if you can copy/ paste one (use the Spoiler code when posting to avoid overly long posts)
I would be interested to see any eso .crash reports which you would find if you open Console:
/Applications/Utilities/Console
And on the left panel click the User Diagnostic Reports drop down menu. An example would be;eso_2014-03-01-142343_xxxusernamexxx.crashYou can copy/paste the text from Console for it *use Spoiler feature as above) or better to use the Attach file feature on this forum editor. It will be in;
~/Library/Logs/DiagnosticReports
On a Mac the '~" means the User. You can navigate to the User Library by pressing Alt and clicking Go in the menu bar to show the Library.
@Chamomile that crash is some other cause as it happened like a quick transition or similar and crash. The memory is not full and client only running for 6-7 minutes. Maybe the Group crash or loading screen problem. Thanks for posting.Cyrodiil crash[reporter]
version = 0.01
[extra]
ProductName = eso
Version = eso.live.1.0.0.962841
char.account = [removed]
char.alliance = 3
char.name = [removed]
client.executablebits = 32
client.mode = teleload
client.renderertype = OPENGL
client.session_start_timestamp = 2014-04-06T03:27:16.948Z
client.time_since_load = 370
client.uptime = 410.7
computer.name = [removed]
computer.user = [removed]
cpu.count = 4
data.depotid = 4000
data.dir = /Applications/ZeniMax Online/The Elder Scrolls Online/game_mac/
data.syncm = databuild
data.version = 0.win.0.live.961669
exe.buildnum = 962841
exe.opt = release
exe.reltype = public
exe.type = client
gfx.description = NVIDIA GeForce GT 650M OpenGL Engine
gfx.deviceid = 0.0.0
gfx.driver = 2.1 NVIDIA-8.24.9 310.40.25f01
gfx.vendorid = 0
globby.address = 198.20.200.162
globby.port = 24505
loc.wloc = 43 331498 26110 421681 275.62
loc.world = Cyrodiil
loc.worldid = 43
loc.zone = Cyrodiil
login.address = 198.20.200.162
mem.current = 2040
mem.peak = 2084
mem.physical = 16384
os.platform = mac
os.version = 13C64
realm.depotid = 0
realm.id = 4000
realm.name = NA Megaserver
reportfield.ver = 3
OK, so we did this in the last beta weekend and it helped a lot to get a fix in for the memory crashes which were happening a lot on a regular basis.
TLDR: Post your ZOSCrashReports here (copy/paste) along with your System details. Instructions of how to do this are included below. For testing, setting Texture Quality to Medium in graphics settings is most helpful.
I thought it may be of interest to give some background and a quick overview of the native Mac ESO client. I'm not a tech guy and tried to keep it fairly simple and understandable for a forum post.
Memory & ESO clients
The ESO Mac & PC clients are 32-bit processes which restricts available memory (address space) to around 4GB regardless of how much RAM you have installed. This is because it was designed to support older computers which is does generally well. But it does cause problems with the newer computers with higher resolutions and graphics settings demanding more and more of this memory.
The Mac & PC operating systems handle memory differently and there are some things specific to developing a game like ESO on the Mac, that require more memory to be used which does tend to make it more liable to memory issues. But PC users also report heavy use of memory in battles though they do not crash as much as it is.
The solution that will alleviate this issue (at least mostly) will be the transition to a 64-bit client. This is something that is already in the ESO development roadmap.
Memory Fix In This Build
The memory fix which is in this build has reduced the frequency of crashes. In normal questing away from lots of people I can go without an issue for 5-6 hours.
The memory crash is very much linked to how any other players are around and of course what graphics settings and resolution are used.
It basically works by automatically reducing Texture Quality once it hits a certain threshold. Doing this reduces the memory requirement a lot as this is the biggest use of available memory. This is a simplistic description of a complex problem.
Current Launch Build Memory Issue
However, under heavy load in the launch build it is happening still and the more reports and feedback we can get to the developers, the better it will be understood. And the memory fix can be altered to reflect what data is collected.
This is especially for AvA in Cyrodiil in big battles where the demands are highest.
In normal questing without lots of players around it should be a lot less evident if at all. This does require players adjusting their graphics setting for best performance v looks which we can add more details on soon to help do this. Default settings are only a best guess and settings need adjusting down especially in PvP.
Posting Crash Reports & Feedback
The most useful thing is for anyone experiencing crashes which are frequent in these situations to post their crash reports to this thread so we have them in once place.
To post your ZOSCrashReports here if you can copy/ paste from the report form it creates on a crash (most times now) and post here with any other details you feel relevant.
Do remove details for privacy if you prefer (public forum) before posting under:
- char.account =
- char.name =
- computer.name =
- computer.user =
Please use the Spoiler code tags around your report to avoid lots of scrolling.
it will look like this:Example of Spoiler tags
You can find that under the Quote option at the top of the post editing window (looks like a backwards P) Just use it like a quote and it will make a clickable drop down window and save a lot of space.
It will also help to include, at least initially, you system details:
Mac System Details
Apple icon (top left of menu bar) > About This Mac > More info…
If you do experience more frequent crashes in PvP then the most helpful thing to do is set Texture Quality down to Medium (or Low depending on existing setting) Also View Distance can be altered via the slider which can help.
For testing Medium Texture Quality (not default graphic setting) will give the most useful data point for now.
Thanks for everyone that has already posted feedback on this. It all helps to improve our Mac ESO client.
The other part of this is to get a better idea of what graphics settings work for people for the different Mac models and which settings can help to reduce issues or improve performance (FPS) I'll post another thread sometime to cover this.
You are right that the ZOSCrashReporter generates reports 'sometimes' after the client crashes. And these get sent to ZOS and the data passed down the line to the developers.
Forgive me for asking, but the Crash report the game it self generates and gets send to ESO is that not the same you are doing.
I cannot see how this in anyway should help since they already have all the info they should need in the crash reports.
Here are my Apple generated crash reports. Is this a global Mac client problem or are there people who are actually able to play without VM crashes?
Thanks for posting this and details @Cudward. it's not the Mac memory issue. Probably related to the ongoing login screen issue.Here's mine ive been getting since about 11pm EST last night, but I haven't gotten more than a minute between these and sometimes it's happening on character load, I sent this to support along with a detailed explaination and ill see what they say but it's unsettling that I played for about 4 hours yesterday and I have spent more time trying to get the client to run than playing.
again, I have had no issues since early access like this I had a few minor crashes but I was up and back at it after those, this one is vexing.
info about my mac
https://www.dropbox.com/s/btty4geac66s4gk/Screenshot 2014-04-07 10.46.52.png[reporter]
version = 0.01
[extra]
ProductName = eso
Version = eso.live.1.0.0.962841
char.account = cudward45
char.alliance = 2
char.name = Khorbyn Lyten
client.executablebits = 32
client.mode = load
client.renderertype = OPENGL
client.session_start_timestamp = 2014-04-07T14:41:10.351Z
client.time_since_load = 17
client.uptime = 91.3
computer.name = Jays-MacBook-Pro.local
computer.user = Cudderr
cpu.count = 4
data.depotid = 4000
data.dir = /Applications/ZeniMax Online/The Elder Scrolls Online/game_mac/
data.syncm = databuild
data.version = 0.win.0.live.961669
exe.buildnum = 962841
exe.opt = release
exe.reltype = public
exe.type = client
gfx.description = Intel HD Graphics 4000 OpenGL Engine
gfx.deviceid = 0.0.0
gfx.driver = 2.1 INTEL-8.24.11
gfx.vendorid = 0
globby.address = 198.20.200.162
globby.port = 24506
loc.wloc = 208 137445 10669 262389 318.16
loc.world = Shadowfen
loc.worldid = 208
loc.zone = Shadowfen
login.address = 198.20.200.162
mem.current = 1239
mem.peak = 1242
mem.physical = 8192
os.platform = mac
os.version = 13C64
realm.depotid = 0
realm.id = 4000
realm.name = NA Megaserver
reportfield.ver = 3
That's great to have thanks @Chamomile. They are all related to the memory crash. The memory issue is in the Mac ESO client. It did have some work done since beta when crashes were worse. Now the frequency outside PvP is reduced but it is still not able to avoid crashing in big battles for more than 20-40 minutes currently. The development team are working to try and address this within the 32-bit client which has it's own constraints. Once a 64-bit client is released it will become pretty much a non issue.Here are my Apple generated crash reports. Is this a global Mac client problem or are there people who are actually able to play without VM crashes?
Useful data to have. They will get passed on.voxtor_turak wrote: »Here's the crash report form DiagnosticReports
Thanks for these.christerb16_ESO2 wrote: »Attaching my set of Apple generated crash logs.
As I explained in the first post in this thread the current situation as I am aware (this is just a distant view as I have little more insight in the ZOS development then others)Publius_Scipio wrote: »@Moonraker thanks for all your work on this issue. You have collected a good deal of crash reports now. Like beta, do you have any idea on a ETA for a fix for this? What I'm asking is that back during beta you were saying you knew a fix was in the works and submitted. Now after launch do you have any knowledge of the matter in terms of what ZOS is up to particularly for this issue?
I would think a fix for crashes would have to be in a patch coming real soon. Since it directly affects a player's game experience.
Thanks for posting.voxtor_turak wrote: »Another Crash report: during a battle in PVE
---snip--
Now the crash report from MacOS
There are certainly a few different issue in Cyrodiil that cause crashing. We do know that there is a specific issue with memory in the Mac client. I have not checked yet from any PC client to see if they have any similar memory out crashes too. The two OS use different methods and also OpenGL > D3D11. The Mac client has to load some more data to memory which leaves less room for any heavy demand. And it appears to leak over time. A combination of the two.This isnt only for Mac users, its affecting Pc users aswell. I personally crash ALL the time in Cyrodill. Send roughly 10-15 reports daily due to client crashes in Cyrodill.
It can help at least to see if it is likely to be the memory issue or not.I guys I haven't really done PvP, but I am crashing ALL the time. About once an hour is about right. Seems like each time there are different triggers, often rollbacks after I log back in.
Would my data be useful?
Hard to say as the memory is not at max on this one but maybe a sudden transition like into building, way shrine etc. may push it over the limit. It's not clear.christerb16_ESO2 wrote: »Crash while running around in Windhelm[reporter]
version = 0.01
[extra]
ProductName = eso
Version = eso.live.1.0.0.964485
char.account =
char.alliance = 2
char.name =
client.executablebits = 32
client.mode = inworld
client.renderertype = OPENGL
client.session_start_timestamp = 2014-04-08T19:52:38.866Z
client.time_since_load = 2650
client.uptime = 2730.5
computer.name =
computer.user =
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.961669
exe.buildnum = 964485
exe.opt = release
exe.reltype = public
exe.type = client
gfx.description = NVIDIA GeForce GTX 680MX OpenGL Engine
gfx.deviceid = 0.0.0
gfx.driver = 2.1 NVIDIA-8.24.9 310.40.25f01
gfx.vendorid = 0
globby.address = 198.20.200.191
globby.port = 24500
loc.wloc = 209 243924 12666 119064 124.78
loc.world = Eastmarch
loc.worldid = 209
loc.zone = Eastmarch
login.address = 198.20.200.191
mem.current = 2330
mem.peak = 2441
mem.physical = 8192
os.platform = mac
os.version = 13C64
realm.depotid = 0
realm.id = 4001
realm.name = EU Megaserver
reportfield.ver = 3