> 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.
Finding them is easy -- you run gnash in normal life, and watch
for your CPU meter to peg. Then attach a debugger to it and see
what it's doing.
Fixing them is more work, requiring understanding how the various
tasks and libraries interact.
John
_______________________________________________
Gnash-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnash-dev
