User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040615 Firefox/0.9 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040615 Firefox/0.9 When attempting to load a XUL page that tries to load the chrome://navigator/skin/ CSS under FireFox, all FireFox instances either die, or hang indefinitely. This has been tested with FireFox 0.9.0 and CVS HEAD from Tue Aug 10 14:44:10 PDT 2004. When run with debugging enabled, the following error message is outputted repeatedly until the application crashes: ###!!! ASSERTION: content sink not found!: 'mSink', file nsExpatDriver.cpp, line 458 Break: at file nsExpatDriver.cpp, line 458 A sample XUL page that exhibits this is attached. Reproducible: Always Steps to Reproduce: 1. Create a XUL application that includes chrome://global/skin and chrome://navigator/skin 2. Load it in FireFox...Crash 3. Load it in Mozilla...the application runs. Actual Results: The application either crashed outright, or hung. Expected Results: The XUL page should have loaded.
I'm getting error in Firefox: XML Parsing Error: xml processing instruction not at start of external entity Location: http://bugzilla.mozilla.org/attachment.cgi?id=155736&action=view Line Number 1, Column 1:
Michael: Could you provide TalkBack incident ID, better from FF093?
Most of the time FireFox only hangs; it crashes intermittently. So, of course, the one time I try to get it to crash to send in an incident report...I couldn't. I manually ran the talkback agent and sent in incident ID TB536601Y anyway.
Manually created incidents are useless, because doesn't contain technical details about crash.
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.