On 04/07/2011 12:54 PM, John Gilmore wrote: > Maybe you can make a 10% or 20% difference with AudioDecoder or > unneeded > malloc/memcpy's. But you can make a 100% difference by fixing the bugs > that cause gnash to spin-lock at times, burning 100% of a cpu core > when > it really has nothing at all to do. Fixing this -- and then seeing > where > else CPU gets used when gnash "should be" idle -- would eliminate the > most > common complaint about gnash, which is that when you install it and > have a couple of flash-using tabs open, it can max out your CPU even > when > you aren't doing anything.
Makes sense. Going through Gnash and identifying these bottlenecks sounds like a big task, though. If finding these bugs prove easy, I could attempt to fix them separately from my main project. However, I don't want to apply for a project that could easily prove very big, and that I don't currently understand fully. The project does sounds interesting, though. Jonas _______________________________________________ Gnash-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-dev
