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.

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.

[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.

• A very short MIDI note at the beginning of a clip would not be audible. [6130]
• Recording via 'Resampling' would not properly compensate latency. [6124]
• Under certain conditions, it would be possible to get 2 Arranger tracks highlighted. [6144]
• Using the Launchpad as control surface and additionally for manual mappings would not always work properly.
• When installing Live Packs which have dependencies to other content, Live would show the corresponding message twice. [6153]
• Using a Rex file could crash Live. [6157]
• 'lock control surface' function would not properly work in user remote scripts. [6064]
• A particular Live set could not be loaded and would lead to a 'Invalid Product ID Error' message. [6165]
• In the Arranger, punch In/Out would delay notes by the 'punch in time' in beats. [6167]
• Using the pads of the Akai MPD18 would not work properly.
• Having a Live set with particular Drum Racks could increase the CPU usage of the main thread, which would result in very slow graphical updates. [6181]
• Installing a new Library from within a second running instance of Live could crash Live. [6171]
• Certain operations like sample crop/reverse/replace would remove the tempo envelope. [6179]
• Using Novation's Launchpad, when switching between Automap and Live control would not work properly.
• Under certain conditions, editing or creating parameter automation would not work properly. [6188]
• Playing a 32-bit audio file immediately after a 16-bit audio file could cause a click in the audio. [6152]
• Moving the last track out of a track group onto a closed group track in the Arranger could crash Live. [6193]
• In the Auto Pan device, switching shape to random would not show the 'Width' knob. [6192]
• Loading a Max device would crash if Pluggo was already active.
• It would not be possible to create a new Project in the File Browser if the root is set to 'Workspace'.
• Fine tuning of macro knobs would not work via key modifier. [6180]
• Starting clips via the Launchpad while changing parameters via mouse could crash Live. [6143]
• Moving the mouse over a certain Sampler preset could crash Live. [6207]
• Loading a Live set containing not yet authorized add-ons could crash Live. [6203]
• Under certain conditions, fade creation would not work properly. [6195]
• An Ableton preset of a third party plug-in would not change the On/Off mapping range. [5652]
• Receiving an invalid parameter index from Max could crash Live.
• Inverting a macro mapping range would not work properly. [6238]
• Under certain conditions, extracting an existing groove from a clip would crash Live. [6235]
• Having a Max device sending many blob changes during saving could crash Live.
• A malformed database file would interrupt user interactions like renaming files, saving presets, recording, etc. [6230]
• Having a particular Live set loaded and searching for media files could crash Live. [6241]
• On Mac OS X, under certain conditions, making Live the foreground window could lead to a crash.
• The context menu of a frozen clip would have enabled audio fades commands. [6253]
• In the Arranger, changing the mixer properties like volume, pan etc. would not show the changed value in the status bar. [3238]
• Having a multi selection of Arranger track and use the 'Show Automation' command would destroy the selection. [6243]
• Choosing a custom VST directory within the preferences would not keep this new directory until the next start of Live if the required rescan leads to a crash. [6190]
• On Mac OS X, duplicating a track with Fab Filter Twin 1+2 could crash Live. [6063]
• The Looper display would use the wrong colour in 'play' mode. [6234]
• Holding SHIFT + Space Bar would make the transport play button flicker. [6227]
• The area to click on an Arranger clip would be too small by a few pixels. [6261]
• Particular Live sets, especially with a lot of transient data, could not be loaded. [6263]
• Pasting 3 unstretched and crossfaded Arranger clips could crash Live [6289]