Closed Bug 362603 Opened 18 years ago Closed 16 years ago

Illegal Operation In Plug-in, Windows Media Player Plug-in DLL (WMP plugin, embedded, crash, JavaScript disabled)

Categories

(Plugins Graveyard :: Windows Media Player (Microsoft), defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: therubex, Unassigned)

References

()

Details

Attachments

(2 files)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060919 SeaMonkey/1.1b
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060919 SeaMonkey/1.1b

Loading target URL causes illegal operation in SeaMonkey - when JavaScript is disabled.

SeaMonkey (usually) crashes (quits) shortly thereafter.

Reproducible: Always

Steps to Reproduce:
1. WMP plugins need to be enabled, npdsplay.dll in particular.
(about:plugins)

2. Disable JavaScript
(edit | preferences | advanced | scripts & plugins | [uncheck] enable javascript for)

3. Load URL, http://gorillamask.net/fgfbomb.shtml
Actual Results:  
Illegal Operation in Plug-in
Windows Media Player Plug-in Dynamic Link Library

The plug-in performed an illegal operation.  You are strongly advised to restart SeaMonkey.

Usually, either immediately, or shortly thereafter, SeaMonkey (crashes) quits.

Expected Results:  
No Crash.
No Illegal Operation in Plug-in

This happens with ...

SeaMonkey 1.0.x/1.8.0.x and 1.1b/1.8.1
Firefox 2.x
(it might not occur in SeaMonkey 1.5a/1.9a1 ?)

WMP10 (10.00.00.4036) or WMP11 (11.0.5744.6324)
Windows XP SP2 or Windows Vista RC2
(for Vista testing, plugins from WMP10 on an Windows XP system are copied into /plugins/ directory on Vista OS)
DLL from WMP, npdsplay.dll (3.0.2.629)
(two other DLL's, npdrmv2.dll & npwmsdrm.dll are not necessary)


This ALWAYS used to occur.  At one point in time, & for a period of time, IT STOPPED - it no longer occurred.   But then it started happening again, & has happened since.


This does not happen with these particular builds:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060916 SeaMonkey/1.1b
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060919 SeaMonkey/1.1b


Starting with this build, the illegal operation has returned:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060930 SeaMonkey/1.1b
Component:, in this bug, perhaps should be Plug-ins, but I don't see a way (that I) can select that?


This is similar to bug 347662, but with current builds I am able to pass the testcase URL listed in that bug.  I do have comments in bug 347662, thinking (incorrectly) that that bug was what I was observing (so if you would review those also).  The testcase URL I used, is also mentioned in bug 347662.

Bug 347662 - [FIX]Windows Media Player Dynamic Plugin Crash Regression
https://bugzilla.mozilla.org/show_bug.cgi?id=347662


Mozillazine thread:

"Illegal operation in Windows Media Player plugin"
http://forums.mozillazine.org/viewtopic.php?t=454548
Assignee: general → nobody
Component: General → Plug-ins
Product: Mozilla Application Suite → Core
QA Contact: general → plugins
Whiteboard: DUPEME
Version: unspecified → 1.8 Branch
duplicate with bug 340262 or with bug 363585 ?
(In reply to comment #2)
> duplicate with bug 340262 

maybe, didn't have time to skim the bug and it's dependencies -- are the regressesions/patches for that only on the trunk??


>or with bug 363585 ?

no, not if it's a regression of a patch checked in only on trunk as it seems likely to be - bug 326273

I saw a comment on the mzine thread that someone had been using a build from 2006 that didn't show the problem.  Could you search for a narrower regression range and provide that info here?
don't know that more than one person tested it, but from mzine: 
"I tried your filecabi.net link in SeaMonkey 1.5a at work. It's the nightly of 20060822. I got the "illegal operation" message popping up. So, either there's some difference in the 20060822 and 20060821 nightlies, or there's some difference in the configuration of SeaMonkey on my two PCs."

Originally what I though I was seeing was this bug, but it is in fact different.
Bug 347662 – [FIX]Windows Media Player Dynamic Plugin Crash Regression
https://bugzilla.mozilla.org/show_bug.cgi?id=347662

I made this comment in that thread with the best range I could come up with.
https://bugzilla.mozilla.org/show_bug.cgi?id=347662#c57

Let me know if I'm wrong, that there were no (Windows) 1.1 builds between 9-20 to 9-29-2006?


I'll also note, which I hadn't realized before, that this bug affects Firefox, or at least:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2pre) Gecko/20070214 BonEcho/2.0.0.2pre
So there is a possibility that I may be able to get a regression range from the FF end?
(In reply to comment #6)
> I'll also note, which I hadn't realized before, that this bug affects Firefox,
> or at least:
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2pre) Gecko/20070214
> BonEcho/2.0.0.2pre
> So there is a possibility that I may be able to get a regression range from the
> FF end?
> 

Yes.
I see no Firefox builds from 2006 at all?

Is what I am seeing correct?
I am looking on ftp.mozilla.org in the nightly directories.

Anywhere else to look?
http://archive.mozilla.org/pub/
No SeaMonkey, but there is Firefox.

Firefox works from 20060909 through 20060927.
Firefox illegal operation from 20060928 through 20060930 (& I checked no further).

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060927 BonEcho/2.0

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060928 BonEcho/2.0
Oops.  This is fallout from Bug 345178
Assignee: nobody → cst
Blocks: 345178
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to comment #10)
> Oops.  This is fallout from Bug 345178
> 

Sorry, wrong bug.
Assignee: cst → nobody
No longer blocks: 345178
CC'ing:  bzbarsky & jst, as they showed up in a bonsai query.
Possibly related to the backout of:
Bug 302737 – [FIX]Plugins leak ns4xPluginStreamListeners and whatever they entrain 
relating to:
Bug 354124 – Flash plugin no longer works with JavaScript disabled
I doubt the bug mentioned in comment 13 is involved here, unless we had this crash back in Gecko 1.7.

What's the regression range including hours?
I'm seeing the illegal operation error also in Mozilla1.7.13, so it's not a (or a very old) regression.
This seems a bit similar to bug 282116.
Blocks: 354124
Attached file Crasher using <embed>
Another way to do this is to type

data:text/html,<embed src="http://gorillamask.net/Media/fgfbomb.wmv">

into the URL bar.
Attached file Crasher using <object>
( code lifted from: http://alistapart.com/articles/byebyeembed )
Here is a Talkback, if that may help.
ID: TB29529741E

AFAIK, there are only two relevant (Windows, Firefox) builds.
So the regression (backout?) range would be 2006-09-27-10-mozilla1.8 to 2006-09-28-11-mozilla1.8


Gecko 1.7 also generates the error.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.13) Gecko/20060711

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041103 Firefox/1.0RC2
I put that file at http://web.mit.edu/bzbarsky/www/testcases/bugs/362603/fgfbomb.wmv to make sure it survives the site going away.

Are we sure this isn't just a bug in the plug-in?
stack is useless :(

http://developer.mozilla.org/en/docs/How_to_get_a_stacktrace_with_WinDbg

comment 15's bug reference sounds about right, offhand
Assuming the premise of the thread so far is accurate ...
 
 
"MS" has released a new Plug-in.
Microsoft® Windows Media Player Firefox Plugin v1.0.0.8
http://port25.technet.com/pages/windows-media-player-firefox-plugin-download.aspx

Using this new Plug-in, NP-MSWMP.dll (wmpfirefoxplugin.exe), rather then the older plugin, npdsplay.dll, effectively masks (or corrects?) the condition I have been seeing.
 
 
Windows XP SP2 (32-bit), Windows Media Player 10
Vista RC2 (32-bit), Windows Media Player 11
I do not know about earlier versions of Windows, nor older versions of WMP.
 
 
Short view:
Works with SeaMonkey 1.0.x & up, & Firefox 1.5.x & up.
Does not work with Mozilla Suite 1.7.x, nor Firefox 1.0.x.
 
 
Appears that NP-MSWMP.dll supersedes npdsplay.dll.  I did not find it necessary to specifically "block" npdsplay.dll (the Windows Media Player Plug-in Dynamic Link Library) by setting the preference item, plugin.scan.WindowsMediaPlayer to some arbitrarily large number, like 999.  Even so, that might be the prudent thing to do.
 
 
The use of NP-MSWMP.dll in Firefox 1.0.x or Mozilla Suite 1.7.x in fact causes a "plugin performed an illegal operation" error message, regardless of whether JavaScript is enabled or not.
 
 
Other things to note ...
 
 
If JavaScript is disabled, some sites, while not generating an error, simply do not work.

Here is one (Amazon Music - Jethro Tull, Aqualung)
http://www.amazon.com/gp/music/wma-pop-up/B00005ASIL001002/

With JS disabled, & npdsplay.dll, you either get a message, "The file you are attempting to play has an extension that does not match the file format.", (MS WMP generates that message) or the media simply does not play.

With JS disabled, & NP-NSWMP.dll, you get music :-)
 
 
SeaMonkey 1.5a
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060725 SeaMonkey/1.5a

1.5a did not appear to be affected by this bug & continues not be be so.
No JS, Jethro Tull, npdsplay.dll = no music.
No JS, Jethro Tull, NP-NSWMP.dll = music.
 
  
Firefox Minefield
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a4pre) Gecko/20070420 Minefield/3.0a4pre

GorillaMask (original URL above) does not work regardless of any settings used.  You are prompted to 'Install Missing Plugins', yet none are found.

No JS, Jethro Tull, npdsplay.dll = no music.
No JS, Jethro Tull, NP-NSWMP.dll = music.
therube, can you get the trace?  (comment 20)
=> incomplete due to no response
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Component: Plug-ins → Windows Media Player (Microsoft)
Product: Core → Plugins
QA Contact: plugins → microsoft-wmp
Version: 1.8 Branch → unspecified
Whiteboard: DUPEME
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: