266789 - ASSERTION: unable to post continuation event: 'Error', file nsStreamUtils.cpp, line 441

Status: RESOLVED WORKSFORME

(Core :: Networking, defect)

Description

[Martin Mokrejs]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041029
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041029

(gdb) 
Continuing.
WARNING: nsExceptionService ignoring thread destruction after shutdown, file
nsExceptionService.cpp, line 191
+++ JavaScript debugging hooks removed.
Abort mail message delivery.
###!!! ASSERTION: unable to post continuation event: 'Error', file
nsStreamUtils.cpp, line 441
Break: at file nsStreamUtils.cpp, line 441
Suspending process; attach with the debugger.


Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[Martin Mokrejs]

Attachment: gdb output

Comment 2

[Martin Mokrejs]

Attachment: one more case

Comment 3

[Boris Zbarsky [:bzbarsky]]

Steps to reproduce?

Comment 4

[Sebastian Tusk]

I get the same assert with the following javascript.

function onload_feedback_wizard()
{
	transport_service =
		Components.classes["@mozilla.org/network/socket-transport-service;1"]
		.getService(Components.interfaces.nsISocketTransportService);
	transport = transport_service.createTransport( null, 0, "mozilla.org", 80, null );
	transport_service = null;
		
	input_stream = transport.openInputStream( 
		transport.OPEN_BLOCKING, 0, 0 );
	transport = null;
	
	// input_stream = null;
}

If input_stream is set explicitly to null, that assert goes away. The script is
part of an application I write using xulrunner. Maybe this problem is unrelated
to that of the bug reporter. 

For reference the assert I get.
###!!! ASSERTION: unable to post continuation event: 'Error', file
c:/Sebastian/dev/libraries/mozilla/xpcom/io/nsStreamUtils.cpp, line 441

Platform is Windows XP SP1.

Comment 5

[Christian :Biesinger (don't email me, ping me on IRC)]

>	input_stream = transport.openInputStream( 

hm... this creates a global variable... and GC can't free it until shutdown of
course

Comment 6

[Gervase Markham [: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/

Comment 7

[Gervase Markham [:gerv]]

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.

Comment 8

[Martin Mokrejs]

See comments #4 and #5. ;)

Comment 9

[Misak Khachatryan]

Is this bug actual ?

Comment 10

[Tony Mechelynck [:tonymec]]

No reply to comment #9 in two weeks -- resolving INCOMPLETE.

Comment 11

[Martin Mokrejs]

I cannot get to reproduce it now due to bug #410486.

Comment 12

[Martin Mokrejs]

Attachment: testcase.html

testcase with the javascript as suggested in comment #4 by Sebastian Tusk (although untested by me yet)

Comment 13

[Martin Mokrejs]

When I take the patch from comment #12 of bug #410486 I get this:

(gdb) c
--WEBSHELL 0x813c8a0 == 6
Document file:///home/mmokrejs/public_html/tmp/testcase-bug266789.html loaded successfully
--DOMWINDOW == 12 (0x821260c) [serial = 14] [Outer = 0x8212430]
--DOMWINDOW == 11 (0x821245c) [serial = 13] [Outer = (nil)]
--DOMWINDOW == 10 (0x82122ac) [serial = 12] [Outer = 0x8211500]
JavaScript error: file:///home/mmokrejs/public_html/tmp/testcase-bug266789.html, line 8: Permission denied to get property XPCComponents.classes
[Thread 0xb1b7eb90 (LWP 15191) exited]

Do not what to do with it so somebody else has to step in and try the testcase. Maybe I got it wrong from comment #4 here. Sebastian Tusk, please? ;-)

Comment 14

[Martin Mokrejs]

(In reply to comment #13)
...
> Do not what to do with it so somebody else has to step in and try the testcase.
--------^ know what to do ...
 

Comment 15

[Serge Gautherie (:sgautherie)]

(In reply to comment #12)
> Created an attachment (id=314349) [details]
> testcase.html

FWIW, Error Console reports:

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9] (release) (W2Ksp4)

{{
Error: uncaught exception: Permission denied to get property UnnamedClass.classes
}}

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9pre) Gecko/2008051603 SeaMonkey/2.0a1pre] (nightly) (W2Ksp4)

{{
Error: Permission denied to get property XPCComponents.classes
Source File: https://bugzilla.mozilla.org/attachment.cgi?id=314349
Line: 8
}}

***

Sebastian,
is this a valid testcase ?
Does it work in at least one build ? (Should it ?)

Martin,
do you have steps to reproduce, other than Sebastian "testcase" ?

Comment 16

[Martin Mokrejs]

Serge, no, I just got it few times while testing devel version ... during shutdown.

Comment 17

[Philip Chee]

Core->Networking

Comment 18

[Boris Zbarsky [:bzbarsky]]

It seems to me like we shouldn't assert this stuff is all... posting the event can fail after shutdown, as in this bug.

Comment 19

[Patrick McManus [:mcmanus]]

this is a warning now