Consistent freezing

Domminust

Since the 2.0.5 patch I am consistently freezing in all areas forcing me to shutdown my computer... The freezes always happened before but would let up in a few seconds.
Game is unplayable now

DaveMoeDee

I get the game freezing like every other day. Does freeze my computer. Just the game.

Definitely not unplayable, but really annoying.

Domminust

Maybe there was just a lot of game traffic at the time.. It seems a bit better in the major zones now and in a delve I am almost 100% smooth.

mavelick

I'm facing this issue too. from the patch 2.0.5. Not playable, and I could not return to Finder on OS X.

radicalb21

After updating 2.0.5 I'm having the game freeze for 5-10 secs then sometimes the game resumes and other times it hard freezes. The only thing I can do then is hold down the power button on my iMac to turn it off. Then restart my system. This happened multiple times in different zones this past evening. I'm currently running OS X 10.10.3 and have 12 GB RAM w/ AMD Radeon HD 6770M 512 MB. I have done a PRAM and SMC reset on my system. I have also repaired launcher as well. I also did repair permissions. Wasn't having these types of issues prior to this patch.

kamimark

Also having this problem. Prior to Monday patch I was getting 15-20 fps in cities, much higher in delves, now it lags down to single digits then freezes entirely, can't even task-switch, have to force reboot the system.

MacBook Air (13-inch, Late 2010)
1.86 GHz Intel Core 2 Duo
4 GB 1067 MHz DDR3
NVIDIA GeForce 320M 256 MB

naturn

Since this last patch my mac has been freezing a lot especially in Cyrodiil. It doesn't just freeze the game. It freezes the whole computer. A few times it suddenly released but mostly I have to restart my computer to continue.
Edit: removed all add ons and 5 minutes in Cyrodiil my mac is frozen solid. It is really hard to pvp when you have to reboot the computer anytime you have a fight.

Imac 27 inch mid 2013
proc: 3.2ghz intel core i5
mem: 24 GB 1600 MHz DDR3
NVIDIA GeForce GTX 675 1024 MB

OS X Yosemite 10.10.3

KhajitFurTrader

I just played for about an hour in Coldharbour, and haven't encountered this phenomenon yet.

I will try again in an hour and visit the more populated places, when prime time on EU should be in full swing.


Update: so now I did some extended "sightseeing", and a little creative pilfering on the side, in the busy cities of the DC. I didn't notice any freezing, though FPS seems a bit lower than in 2.0.4, with the same graphics settings, but the lows were still well over 25.

Beats me.

chris.dillman

Some threading affinity / priority code was put into Mac ESO with this last patch.
This code matches whats running on PC / Console version of the game.

Now the new thread code works by suggesting to the OS that
threads run at higher or lower priority or that they sit on just 1 CPU core and don't jump around.
It is a possibility that this has lead to some kind of task starvation on older
hardware like the Core2 Duo Mac Book air listed above.

So far on our test machines we are not seeing this bug
and FPS are up and game play is generally smoother.

So to help us narrow the problem down..

What OS version is everyone running?

What hardware?

Also note that OSX 10.10.3 just shipped and may contain issues.

PS: Everyone please turn off all Add ons when testing.

chris.dillman

naturn wrote: »

Since this last patch my mac has been freezing a lot especially in Cyrodiil. It doesn't just freeze the game. It freezes the whole computer. A few times it suddenly released but mostly I have to restart my computer to continue.
Edit: removed all add ons and 5 minutes in Cyrodiil my mac is frozen solid. It is really hard to pvp when you have to reboot the computer anytime you have a fight.

Imac 27 inch mid 2013
proc: 3.2ghz intel core i5
mem: 24 GB 1600 MHz DDR3
NVIDIA GeForce GTX 675 1024 MB

OS X Yosemite 10.10.3

Hi Naturn

If you run ESO in windowed mode.
and go Cyrodiil is the ENTIRE mac locking up or just ESO?

PS: Everyone please turn off all Add ons.

gary.mcleodeb17_ESO

Same issues on my iMac, tonight game locked up in Mournhold once, but in Cyrodiil, I was unable to take part in any pvp exchanges due to radical freezing as described already. Four times in 20 minutes. This can't be good for my iMac.

Required to switch off and then restart due to system being entirely unresponsive.

iMac late 2012
2.9 Ghz intel i5
8 GB 1600 MHz DDR3
NVIDIA geForce GT 650M 512 MB

I'm at a complete loss as to what to do next.

Removed any apps operating at same time... reduced all video settings to low, removed launcher app after start-up. Repaired x 2.

Recent TESO patch this morning.

Don't know what else to say other than I'm quite concerned by what's happened.

LoadingScreen

same problem:

iMac late 2013
yosemite 10.10.3
3.4 ghz i5
32gb 1600 mhz ddr3
nvidia gtx 780m 4096mb

TikiGamer

My work colleague who I was grouped with this evening had the same problem.

His machine:
iMac mid 2010 27”, quad core 2.8 i5, 16Gb, ATI Radeon 5750 1024Mb -  latest OS/X 10.10.3  

Looks like a scheduling issue in the OS, got the kernal panic spinning ball. Monitoring of threads showed no significant increase in cpu nor did ram usage increase, but system became unresponsive. mouse/cursor still moved.

TikiGamer

I should also note that I did not experience this on my late 2013 retina Macbook Pro - though I had one loading screen that took 2 minutes, but I think that was general lag

mavelick

I removed the depot folder and re-download all contents, but not solved.
I faced this issue in Rawl'kha in Reaper's March.
Sometime, I can back to game with wating 5-10 sec. In other case, I get back to login form after freezing a cupple of minutes.

iMac (Retina 5K, 27inch, Late 2014)
3.5 GHz Intel Core i5
32GB 1600MHz DDR3
AMD Radeon R9 M295X 4066MB

Mac OS X Yosemite 10.10.3

radicalb21

Mac OS X Yosemite 10.10.3
iMac 21.5 (Mid 2011)
2.7 GHz Intel Core i5
12 GB 1333 MHz DDR3
AMD Radeon HD 6770M 512 MB

Still have issues in game with freezing for 5-10 secs then the game resuming or the other side of the coin where the system locks up and have to do a hard reset. This is without running any add-ons. Any and all suggestions would be appreciated from forums poster and developers. Framerate is fine and operating in normal levels.

Bouvin

Been happening to me since 2.x.

I think the issue is wide spread based on talking to other people in game.

radicalb21

My game was running fine prior to patch 2.0.5. Mac OS X Yosemite 10.10.3 was released on April 8 2015 in which in ESO I was running patch 2.0.4 with no freezing issues whatsoever or system lockups. So I would say its the change you made this week that caused this issue to happen. Another issue that is still ongoing is the loading of textures in some zones in game that take way to long to load. It would also be nice to know when changes are coming to MAC client as the forums have been kinda quite. Any and all help would be appreciated.

shivadevaux

I haven't experienced any lockups during my play time yesterday (MacPro late 2013 running OS X 10.9.5), but when the game freezes, have you tried force quitting the ESO app by pressing Command, Shift, Alt, Esc together and holding the keys for several seconds? Worked for me back in the day (last year when a new build of the game would often crash my ESO app and I couldn't get back to the desktop to manually quit it since I was/am playing fullscreen).

Hope this helps

radicalb21

Nothing works once the system freezes except using the power button. Tonight alone my system has completely frozen multiple times (5x), Three of the times I was in Bruma entering the church when the game froze completely. The other times I was just walking around in belkarth and stormhaven. This is getting to the point where it is unplayable. They really need to fix this before next week. If this continues for much longer I will stop playing this game altogether and will not recommend this game to any of my friends.

kamimark

chris.dillman wrote: »

What OS version is everyone running?

OS X 10.10.3, but it worked fine with patch 2.0.4.

I went in and disabled all addons, and either that kept it alive longer, or just the lower night population is crashing it slower. It ran under 10 minutes before crashing. My normal addon list is:

AdvancedFilters
Durability
HarvensQuestJournal
HarvensStackSplitSlider
HarvensTraitAndStyle
LootDrop
LoreBooks
LostTreasure
MasterMerchant
NoThankYou
RainbowReticle
RareFishTracker
SkyShards
VotansFisherman

LoadingScreen

OS X 10.10.3, but it worked fine with patch 2.0.4.

same!

chris.dillman

Hi everyone.

Please disable add ons and try running the game in a window.
Then report back if the ENTIRE machine crashes or just ESO locks up.

We have not seen this on any of our test machines yet.

If the entire machine locks up when ESO is running in Windowed mode
Its possible we have hit an issue in 10.10.3
Or we have over optimized ESO in such a way that it is causing certain older macs to over heat.

TikiGamer

chris.dillman wrote: »

Hi everyone.

Please disable add ons and try running the game in a window.
Then report back if the ENTIRE machine crashes or just ESO locks up.

We have not seen this on any of our test machines yet.

If the entire machine locks up when ESO is running in Windowed mode
Its possible we have hit an issue in 10.10.3
Or we have over optimized ESO in such a way that it is causing certain older macs to over heat.

Sometimes just a short freeze, but also causing entire Mac to lock. Running in window with addons disabled. Only since EU patch yesterday.

defyflesh

This has been happening to me as well.
I'll take about 10 steps in game and my Mac will completely freeze making me force shut down the computer.
Even in windowed mode.
I don't run any add ons.
My Mac does get exceptionally hot while playing.
It worked fine before the patch.

Macbook pro 2009
2.66 GHz Intel Core 2 Duo
4 GB 1067 MHz DDR3
NVIDIA GeForce 9400M 256 MB
OS X 10.9.5 (13F34)

Thanks for any help.

Randay

also having same issues starting from last patch.

found this in console:

Apr 15 17:06:43 localhost AwesomiumProcess[452]: The function ‘CGFontSetShouldUseMulticache’ is obsolete and will be removed in an upcoming update. Unfortunately, this application, or a library it uses, is using this obsolete function, and is thereby contributing to an overall degradation of system performance.
Apr 15 17:07:02 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:02 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:02 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:02 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:02 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:02 localhost WindowServer[138]: Surface test allowed updates after 13 attempts
Apr 15 17:07:02 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:02 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:02 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:02 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:03 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:03 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:03 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:03 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:03 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:03 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:03 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:03 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:03 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:03 localhost WindowServer[138]: Surface test allowed updates after 10 attempts
Apr 15 17:07:04 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:04 localhost WindowServer[138]: Surface test allowed updates after 12 attempts
Apr 15 17:07:04 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:04 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:04 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:04 localhost WindowServer[138]: Surface test allowed updates after 15 attempts
Apr 15 17:07:04 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:04 localhost WindowServer[138]: Surface test allowed updates after 12 attempts
Apr 15 17:07:04 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:04 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:04 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:04 localhost WindowServer[138]: Surface test allowed updates after 14 attempts
Apr 15 17:07:05 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:05 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:05 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:05 localhost WindowServer[138]: Surface test allowed updates after 15 attempts
Apr 15 17:07:05 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:05 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:05 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:05 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:06 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:06 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:08 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:08 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:08 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:08 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:08 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:08 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:09 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:09 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:09 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:09 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:10 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:10 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:11 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:11 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:12 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:12 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:12 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:12 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:13 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:13 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:16 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:16 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:17 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:17 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:18 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:18 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:21 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:21 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:21 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:22 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:22 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:22 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:27 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:27 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:28 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:28 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:29 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:29 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:29 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:29 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:32 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:32 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:33 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:33 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:35 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:35 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:35 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:35 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:36 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:36 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:36 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:36 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:36 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:36 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:39 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:39 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:39 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:39 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:41 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:41 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:43 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:43 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:44 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:44 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:45 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:45 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:07:45 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:07:45 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:19:35 localhost bootlog[0]: BOOT_TIME 1429111175 0

Randay

what i did now is:

1. start launcher
2. start game
3. login
4. select character and click play
=>then the errors start to appear

Here my ASL from starting the laucher until i was in game:

Marker - 15.04.2015 17:43:13
Apr 15 17:43:25 --- last message repeated 7 times ---
Apr 15 17:43:25 localhost kernel[0]: Sandbox: mdworker(422) deny file-read-data /Users/xxxx/Library/Preferences/com.apple.security.revocation.plist
Apr 15 17:43:55 --- last message repeated 3 times ---
Apr 15 17:44:13 localhost sandboxd[166] ([417]): mdworker(417) deny file-read-data /Users/xxxx/Library/Preferences/com.apple.security.revocation.plist (import fstype:hfs fsflag:480D000 flags:250000025E diag:0 isXCode:0 uti:com.apple.application-bundle plugin:/Library/Spotlight/Application.mdimporter - find suspect file using: sudo mdutil -t 3105313)
Apr 15 17:44:13 localhost sandboxd[166] ([417]): mdworker(417) deny file-read-data /Users/xxxx/Library/Preferences/com.apple.security.revocation.plist (import fstype:hfs fsflag:480D000 flags:250000025E diag:0 isXCode:0 uti:com.apple.application-bundle plugin:/Library/Spotlight/Application.mdimporter - find suspect file using: sudo mdutil -t 3105313)
Apr 15 17:44:39 --- last message repeated 2 times ---
Apr 15 17:44:39 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:39 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:44:39 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:39 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:44:39 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:39 localhost WindowServer[138]: Surface test allowed updates after 14 attempts
Apr 15 17:44:39 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:39 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:44:39 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:39 localhost WindowServer[138]: Surface test allowed updates after 12 attempts
Apr 15 17:44:39 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:39 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:44:39 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:39 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:44:39 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:39 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:44:40 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:40 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:44:40 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:40 localhost WindowServer[138]: Surface test allowed updates after 14 attempts
Apr 15 17:44:40 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:40 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:44:40 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:40 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:44:40 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:40 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:44:40 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:40 localhost WindowServer[138]: Surface test allowed updates after 12 attempts
Apr 15 17:44:40 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:40 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:44:40 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:40 localhost WindowServer[138]: Surface test allowed updates after 11 attempts
Apr 15 17:44:40 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:40 localhost WindowServer[138]: Surface test allowed updates after 14 attempts
Apr 15 17:44:40 localhost WindowServer[138]: Surface testing disallowed updates for 10 sequential attempts...
Apr 15 17:44:40 localhost WindowServer[138]: Surface test allowed updates after 15 attempts
Apr 15 17:45:02 localhost AwesomiumProcess[464]: The function ‘CGFontSetShouldUseMulticache’ is obsolete and will be removed in an upcoming update. Unfortunately, this application, or a library it uses, is using this obsolete function, and is thereby contributing to an overall degradation of system performance.

KhajitFurTrader

iMac (27-inch, Late 2013)
3,5 GHz Intel Core i7
32 GB 1600 MHz DDR3
NVIDIA GeForce GTX 780M 4096 MB
512 GB PCIe SSD as Macintosh HD

OS X 10.10.3 (14D131)

No addons at all, game running in fullscreen @2560x1440, High quality

No freezes yet seen in 2.0.5, smooth gaming experience.

Alkeo

I'm having the same problem with a late 2009 iMac. I was playing fine on med resolution prior to 2.0.5. Now, within 10 mins or so of playing it will completely lock up the computer in windowed or full-screen mode, with or without add ons enabled. This requires a hard reboot (turn power off). There is no other way to recover.

KhajitFurTrader

I put the game into windowed mode and looked at CPU core load distribution while playing in Coldharbor and Wayrest on EU, using iStat Menus.

I saw a quite even distribution of load on all 4 cores at all times on my Haswell Core i7. The single load on a core went barely over 50%, and if so, it was only for very short times.

Alkeo

Alkeo wrote: »

I'm having the same problem with a late 2009 iMac. I was playing fine on med resolution prior to 2.0.5. Now, within 10 mins or so of playing it will completely lock up the computer in windowed or full-screen mode, with or without add ons enabled. This requires a hard reboot (turn power off). There is no other way to recover.

After installing ESO on my Mid-2012 Macbook Pro and playing for about an hr, I haven't had a lockup. However, my iMac freezes every time and it was working fine with 2.0.4.