* Mike Hommey: >> Even if the browser cannot be restarted after the attack has been >> carried out? The impact of this bug is slightly different from other >> crash bugs. > > Are you sure the firefox process was not still running ? That would > explain the browser not being able to restart...
According to the Mozilla Foundation, the exploit causes Firefox to spent a lot of CPU cycles on startup. The browser eventually starts, but it will take a long time (several minutes) on some machines. Here'se the analysis: <http://www.mozilla.org/security/history-title.html> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
