That was asked earlier also - first chance to answer.
When a programmer needs a buffer area, he defines and declares it, and that's up to the compiler / OS to satisify.
In this case, he kinda just said, hey - gimme a buffer.
The system is warning the dev that this works, but is subject to the whims of updates and and also, he needs to be consistent in his buffer use.
In some software shops, the practice is allowed, freeing the dev to think in abstract terms.
In other shops, the practice is frowned upon as not sufficiently disciplined, and the dev ought say: Hey, I require a buffer of exactly the following size...
Old-school guys are typically firmly in the second camp.
The message is marked with an I for information.
I found it quite odd that the resets were also marked the same way, though, in Mr. Ed's logs, while marked with a D for debugging output by the dev in the Awesome Player output above.
Reading too much into the letter codes unless it's a W for Warning or E for Error is a path to second guessing and therefore darkness.
Hope that helps or clarifies.
PS - if you guys wrap your logs with hide tags, this page will shorten and scroll better. Look for the big H on the right under Advanced.
skippity skip skip. If the buffer process is interrupted (most likely due to network and in my case while driving through multiple towers) it skips. plain and simple. The question....why is the Evo buffering the stream when the Aria is not. The aria appears to be actually streaming it. If the stream is interrupted, it just looks until it picks it back up again. 
