After clicking a button on a page I use frequently (Westlaw), I consistently get the following message: "The procedure entry point NS_NewArrayEnumerator could not be located in the dynamic link library xpcom.dll" This is happening in a password-protected site so, sorry, no way to give you a URL to test. I did, however, find the java subroutines which are being run by the button & would be happy to pass them on to whoever might find them helpful. The error is repeatable and only occurs in Phoenix.
If you have the subrutines could you post an example of the java that caused the error here, or maybe a copy of a page causing the error? That would make it far easier to reproduce. If you like you can create an attachment of a copy of the page as a testcase to this bug using "create new attachment". :)
J Glusman, have you tried the most recent builds available from: http://ftp.mozilla.org/pub/phoenix/nighty/latest-trunk/ Please try installing that build into a clean directory (don't overwrite an old installation) and also create a new profile with phoenix.exe -ProfileManager. Report back at http://bugzilla.mozilla.org/show_bug.cgi?id=176074 with your findings.
I think I have egg on my face (but don't really know why that should be...): In the past, I had: 1. dropped the "Phoenix" folder into the existing Program Files directory, confirming overwrite, and 2. for the 0.4 release, deleted my profile (using profile manager) and created a new one as instructed This time, I: 1. trashed both the program and settings folders, and did a clean install of the latest nightly build, and 2. recreated my preference settings, in case something about cookies or java was causing the problem The problem has apparently disappeared.
Just to confirm, when I say "dropped the Phoenix folder" into the program files directory, I mean that I dropped the folder called "Phoenix" into a directory which contained another folder called "Phoenix."
Thanks for this information. Marking INVALID. Sometimes the release notes DO contain important stuff:-)
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.