Nanofunk Blog Main Site

Geek blog for all things hackintosh, dslr video plus tweaking, hacking and modding your gear and gadgets.

22Dec/112

kernel[0]: IOSurface: buffer allocation size is zero – A never-ending story about Adobe failing to get their Flash Player and Adobe Air Plugin to work on Mac OSX in a “normal” way.

kernel: IOSurface: buffer allocation size is zero
kernel[0]: IOSurface: buffer allocation size is zero

With Mac OSX Lion 10.7.0, a message was repeatedly showing up in the Console.app, so the logfiles would grow in size - sometimes around 100 MB per minute. This is especially bad for SSD owners. While the issue was reported over 6 Months ago, and Flash Player 11 solved the amount of errors in the console, still the message appears and slows down OSX 10.7 systems.

At least the release of Adobe's Flash Player 11 solved the system freezes - but the Log message still is filling the kernel.log, so any debugging or search for errors is quite hard with that amount of data to read through.

If you are experiencing the same issues, please write your concerns to the Adobe Forums in the existing thread and alternatively also in the Apple Discussion Thread.

Nanofunk reported about this issue in july 2011, and we got over 60.000 unique visits to this post - so this is not a rare case, this is a serious bug with Adobe Flash and Adobe Air. We will post any updates to the situation to this blog, make sure to bookmark our feed.

See also:
* macrumors forum about kernel: IOSurface: buffer allocation size is zero
* nanofunk: Mac OSX Lion 10.7 System Freezes: kernel: IOSurface: buffer allocation size is zero (console message)

 

[Update] I posted to the Adobe Bugbase with a bug description. Hope they will respond now.

28Jul/1142

Mac OSX Lion 10.7 System Freezes: kernel: IOSurface: buffer allocation size is zero (console message)

Some people experience system freezes on Mac OS X 10.7 Lion, but also on Snow Leopard: kernel: IOSurface: buffer allocation size is zero.
The Error is visible with Console.app ("All Messages" respectively "kernel.log")

To reproduce the issue:
1) click on "Clear Display" in Console.app
2) go to http://www.adobe.com/software/flash/about/ and the error will show up in the console.

The error must be Flash related. Sometimes, the whole System is unresponsive, freezing everything but the mouse. There is no official response from Adobe or from Apple, so we can only hope and wait. Please check your Console.app for this error and respond to any of the existing discussions.

Screen Shot 2011 07 28 at 11 52 25

[Update] the error message also seems to have surfaced in 10.6.4 already, as visible in the Apple Discussion Forums

[Update] installing the Adobe Flash Player 11.0 from Adobe Labs seems to at least minimize the freezes, but still the console messages appear.

[Update] i posted a poll on insanelymac to see which browsers and systems are affected. please also post your results there!

[Update] the new Beta 2 11.0.d1.98 of the flash player is out (thanks JP Hansen)

[Update] The Flash Player 11 is officially released. It seems though, that not all issues are resolved with Mac OSX Lion compatibility.

[Update 23.12.2011] more than 6 months after the issue was reported, (and we have Apple Mac OS X 10.7.2 and 10.7.3 in beta) there is still no update on this issue from Adobe. Please write your concerns to the Adobe Forums in the existing thread to have them fix the issues! Especially for SSD owners this is unacceptable!

Existing Discussions:

* Nanofunk.net discussion thread in the Adobe Flash Player Forums
* Thread in the Apple Support Communities Forum
* Thread on MacRumors Forums regarding Lion Freezes with kernel: IOSurface

[Update] I posted to the Adobe Bugbase with a bug description. Hope they will respond now. Please, support our effort by filing another report at the Adobe Bugbase!

[Update 2012-2-22] still, the ticket in Adobe Bugbase is open, although there were several patches and bugfixes to Adobe Flash Player 11.1 (11.1.102.62 as of today).

[Update] Adobe recently closed the bug report. This is very bad news, since lots of people are experiencing this issue. I cannot believe how bad the Adobe support and bugfixing guidlines are.

   
..