On 25.06.2008 20:47, Trevor Hemsley wrote:
> As the subject, I have Seamonkey 1.1.9 running and accidentally opened the Tools
> -> Web Development -> JavaScript Debugger option. It locked up SM for about a
> minute and then successfully started the JS debugger (which surprised me, but
> thank you). I closed it down as soon as it started but half my web pages are now
> taking minutes to repaint after hitting the back button in the browser. CPU
> Monitor shows the CPU usage using one of my two CPUs at 100%.
Hmm, it doesn't happen to me. I take it that you have tried to at least
restart SeaMonkey afterwards (and perhaps also reboot the system)?
I have no idea what could be causing either the initial delay when
starting the JS Debugger nor the subsequent slowness when loading pages.
AFAIK that tool doesn't have platform specific parts, so this might not
be tied to OS/2.
I'm cross-posting this to mozilla.dev.apps.js-debugger to get input from
people who actually know that tool.
--
Please Enhanced OS/2 builds of Mozilla applications
reply in
http://pmw-warpzilla.sf.net/newsgroup
Steve's Warpzilla Tips:
http://www.os2bbs.com/os2news/Warpzilla.html_______________________________________________
dev-apps-js-debugger mailing list
dev-apps-js-debugger@...
https://lists.mozilla.org/listinfo/dev-apps-js-debugger
