239762 - Statusbar wrong displayed when plugin using NPN_PostURLNotify

Status: RESOLVED EXPIRED

(Core Graveyard :: Plug-ins, defect)

Description

[Ginn Chen]

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

Statusbar displayed progress information in wrong window

Reproducible: Always
Steps to Reproduce:
1.Open Mozilla, browse a webpage using plugin NPN_PostURLNotify method in window(A).
2.New a Mozilla window(B), browser a webpage using plugin NPN_PostURLNotify method


Actual Results:  
The status information for window(B) displayed under window(A) wrongly.

Expected Results:  
The status information for window(B) should display under window(B).

Comment 1

[Ginn Chen]

Plugin can only call NPN_PostURLNotify in its main thread.
I think it's the problem, Mozilla can't which window called the method.

If plugin call NPN_PostURLNotify in a new thread, nsHttpTransaction::Init method
got 0 for queue, this will cause a Segmentation Fault. After that, Mozilla can't
send/receive and stream.

###!!! ASSERTION: ouch: 'queue', file nsHttpTransaction.cpp, line 157

[New Thread 11276 (LWP 4709)]
###!!! ASSERTION: You can't dereference a NULL nsCOMPtr with operator->().:
'mRawPtr != 0', file ../../../dist/include/xpcom/nsCOMPtr.h, line 670

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1026 (LWP 4694)]
0x40e22d08 in nsTransportEventSinkProxy::OnTransportStatus(nsITransport*,
unsigned, unsigned, unsigned) (this=0x82afa30, transport=0x0, status=2152398851,
    progress=0, progressMax=0) at nsTransportUtils.cpp:169
169             rv = mTarget->PostEvent(event);

Comment 2

[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 3

[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.