User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 When I entered the page thorugh Google, it just crashes. As it is a Chinese site, I opened HansVision to view it, but the next thing, when I viewed the page, the browser suddenly closes itself, and inserts a hss_err_pid4.log into the Mozilla Firefox folder. Reproducible: Always Steps to Reproduce: 1. Open Hansvision 2. Go to the site Actual Results: The browser closes itself automatically, and left a hss_err_pid4.log in the Mozilla Firefox folder. Expected Results: The browser should not close the window, or it should ask for permission before closing.

This looks like a Java crash to me (hss is Hot Spot Server), and is not security-sensitive. Gerv

This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/

This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.