On 04/07/2011 09:42 PM, John Gilmore wrote:
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.
In that case, it sounds like I can work on these bugs in parallel to my
main GSoC project (whenever I encounter them). It would also be a good
way to learn how the various subsystems of Gnash works.
Jonas
_______________________________________________
Gnash-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnash-dev
