265.11 KB, image/png
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 hi every time i'm trying to access via https to my Web-based Cisco PIX Device Manager 3.0 the Firefox crashes after few seconds after the page is loaded. I don't know any other type of information i can give.. what else i should do? to provide you more info? Thanks Reproducible: Always Steps to Reproduce: 1. acees https://pixip 2. login 3. wait few seconds and crash I've updated to Firefox 1.0 by uninstalling the previous firefox, deleting the program folder, but not deleting the profile folder.
Summary: Crach accessing Cisco PIX Device Manager → Crash accessing Cisco PIX Device Manager
Version: unspecified → 1.0 Branch
reporter: please install talkback, when you crash you should be able to run components\talkback.exe and copy the incident id to this report. if you could provide access to your pix, that'd be good :).
Severity: normal → critical
Keywords: crash, stackwanted
I've also noticed that if you run Cisco PDM (6.1), quitting the session will often cause unpredictable behavior in Firefox (typing address in the address bar is reversed, Firefox quits on the GUI level but the process is still running, etc.)
Please, lets stay away from bug creap. This issue is for Firefox crashing when you attempt to log onto Cisco PIX Device Manager 3.0. If you have any othe bugs feel free to open one.
Well..i wish to use talkback..but even if the talk back agent is turned on, when Firefox crashes the agent doesn't appear..and firefox close. Sorry, but as u can immagine, i cannot give you access to the PIX :)
Does this occur with the latest Sun Java 1.5.0? This fixed the backwards text issue, perhaps the crash issue is also resolved?
Yes it occurs even if i have jre 1_5_0_01, this under windows. Under linux instead it works perfectly even if the jre is 1.4.
well.. maybe i've found the problem: At first i have to say that i've uninstalled the firefox 1.0 (not deleted the profile but just the program) and installed the new 1.0.1 version. I've noticed that if i Accept the certificate just for the current session (i've translated it from italian message that appears) the firefox crashes, but if i accept the certificate "always" it works perfectly.. i've tryed it several times, with the same result. Bye
I have experienced the same issue, but not only with Firefox but also with IE. Appears to be a java issue. There is a workaround for this: while the dialog shows "loading data from pix" (or something like that the main form show "home", "configuration" and "monitoring" buttons. Start clicking the Configuration button until the configuration page appears and you can configure your PIX without crashes. Do not switch back to the Home page.
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.