|
High CPU and log spamming
I'm running the latest 2.4 beta 2. Overall working pretty well but for some reason today I'm getting high CPU and a lot of spam coming through in the syslog like this:
Code:
WindowServer[234] <Error>: allocate_backing_surface : IOAccelCreateSurface = e00002c7 |
1 Attachment(s)
Nope, but that sure looks like DisplayLink driver vs WindowServer again... I see it too in my console log...
Sigh... I've ran the "DisplayLink Information" support tool to gather information about my Mac, with the latest 2.4 (no beta) driver installed, but without both DisplayLink monitors disconnected. I'll run this tool again when both DisplayLink monitors are connected (perhaps there's a difference in output?). I uninstalled the last beta of 2.4, rebooted, installed the official 2.4 driver, rebooted and then connected one DisplayLink monitor, followed by the other as soon as the first showed me a desktop (just to be sure no firmware updates were in progress). Later today, I (again) had a frozen MacBook. Only the mouse was responding, nothing else. The usual trick to get everything working again without rebooting, didn't help unfortunately, I had to force shutdown my MBA. The usual trick is to unplug the USB connection and wait until al opened windows appear on the internal screen of my MBA, and then replug it again. |
For the record, the level of this message:
Code:
28-07-15 15:26:16,750 WindowServer[155]: allocate_backing_surface : IOAccelCreateSurface = e00002c7 |
1 Attachment(s)
And information from the DisplayLink Information tool when both DisplayLink monitors are connected is attached to this message.
|
Thanks for chipping in with your experience as well.. let's hope this is sorted soon!
|
I'm also getting this "IOAccelCreateSurface = e00002c7" in my log
I have this problem too -- it hits the log whenever I switch desktops (spaces) in the DisplayLink displays -- or if I activate a window in a DisplayLink display.
(I'm running a pair of LT1421 displays using a MBP 13" 2012, if that helps -- and this happens with/without a usb hub between my MBP and the displays.) Here's a sample of my log. 2015-08-15 12:03:53.345 PM WindowServer[143]: allocate_backing_surface : IOAccelCreateSurface = e00002c7 2015-08-15 12:03:53.346 PM WindowServer[143]: allocate_backing_surface : IOAccelCreateSurface = e00002c7 2015-08-15 12:03:53.987 PM WindowServer[143]: allocate_backing_surface : IOAccelCreateSurface = e00002c7 2015-08-15 12:03:53.988 PM WindowServer[143]: allocate_backing_surface : IOAccelCreateSurface = e00002c7 2015-08-15 12:03:54.099 PM WindowServer[143]: allocate_backing_surface : IOAccelCreateSurface = e00002c7 2015-08-15 12:03:54.251 PM WindowServer[143]: allocate_backing_surface : IOAccelCreateSurface = e00002c7 2015-08-15 12:03:54.251 PM WindowServer[143]: allocate_backing_surface : IOAccelCreateSurface = e00002c7 2015-08-15 12:03:54.253 PM WindowServer[143]: allocate_backing_surface : IOAccelCreateSurface = e00002c7 2015-08-15 12:03:54.953 PM WindowServer[143]: allocate_backing_surface : IOAccelCreateSurface = e00002c7 2015-08-15 12:03:54.954 PM WindowServer[143]: allocate_backing_surface : IOAccelCreateSurface = e00002c7 Please let me know if you need any more information to debug this. |
I use one DisplayLink monitor as my main screen, the second for more static stuff, like mail, calendar and Slack. I don't use spaces that much, but occasionally I do. But I see these lines more often than I switch a space. But then again, I use two DisplayLink monitors so I'm activating different windows quite a lot.
Can you, by any chance, narrow things down? Perhaps I can reproduce it? |
| All times are GMT. The time now is 08:49 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.