Closed Bug 124428 Opened 23 years ago Closed 23 years ago

URLNotify not called if plugin is destroyed before NPP_NewStream is called

Categories

(Core Graveyard :: Plug-ins, defect)

x86
Windows NT
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 127259

People

(Reporter: aberger, Assigned: serhunt)

Details

From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0) BuildID: 0.9.4 branch When the plugin is being destroyed, mozilla cleans up its streams by destroying them and calling NPP_UrlNotify. In general, we do receive Notify (unlike bugs 117766 and 117770, because we have a NULL target and non-NULL notifyData). In 2 cases we do NOT get notified. 1) The plugin is destroyed between the time we call GetURLNotify and the time you call NPP_NewStream. 2) If we return an error from NPP_NewStream (we cancel the stream during NewStream- we decide we don't want it after all. My assumption is that you call notify on all streams in your array. Is it possible that streams don't get placed into the array until after NPP_NewStream returns with no error? Reproducible: Sometimes Steps to Reproduce: 1.This is not too easy to reproduce because it is a timing issue- you need to close the page with the plugin or hit refresh between the time that the stream is requested and the time NewStream is called. Maybe the sample plugin is the easiest way? If you want to try using our plugin, let me know, and I will try to post instructions. But i don't think that is the easiest way to go.
marking new...
Status: UNCONFIRMED → NEW
Ever confirmed: true
nominating nsbeta1, mozilla1.0, 4xp
Keywords: 4xp, mozilla1.0, nsbeta1
problem 2) is fixed by check in for bug 123974
Issue #1 will be fixed in bug 127259. *** This bug has been marked as a duplicate of 127259 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.