Closed Bug 500654 Opened 15 years ago Closed 15 years ago

Fix OS/2 plugin code similar to bug 493601

Categories

(Core Graveyard :: Plug-ins, defect)

x86
OS/2
defect
Not set
normal

Tracking

(status1.9.1 .3-fixed)

VERIFIED FIXED
Tracking Status
status1.9.1 --- .3-fixed

People

(Reporter: mozilla, Assigned: dragtext)

References

Details

(Keywords: verified1.9.1)

Attachments

(2 files, 1 obsolete file)

I can't see what bug 493601 is really about (it's still hidden) but as one can see e.g. in bonsai (for the checkin on CVS trunk)

http://bonsai.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&subdir=mozilla/modules/plugin/base/src&command=DIFF_FRAMESET&file=nsPluginNativeWindowWin.cpp&rev1=1.28&rev2=1.29&root=/cvsroot

it changes functions that until now were mostly in sync with OS/2. The checkin comment is "Fix crash involving Flash module unloading". I guess this would be relevant for mozilla-central, mozilla-1.9.1 and 1.9.0=CVS-trunk.

Maybe this can help to make us more stable even though we have this unstable flash?
This largely a port of changes to the Win32 version of nsPluginNativeWindowXXX.cpp.  Whether it actually does anything worthwhile remains to be seen.  There are also some formatting changes to improve consistency & readability.
Attachment #390740 - Flags: review?(mozilla)
Great, looks like that way you found fixes for some other crashes that could appear like Flash problems (like bug 374229 and the ancient bug 131007). I guess even if we don't take the sWM_FLASHBOUNCEMSG stuff we should add the rest. I don't like :: if they are not required, but OK. The
   sPluginNativeWindowOS2 * win
before the NS_ASSERTION should get an #ifdef DEBUG around it, to circumvent the warning.

Because of the plugin situation on trunk I ported the patch to the 1.9.1 branch to get wider testing. The DLL in this ZIP file:
   http://temp.weilbacher.org/bug500654_gkplugin_20090726_191.zip
goes together with the nightly SeaMonkey build from here:
   http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/2009/07/2009-07-26-04-comm-1.9.1/
Assignee: nobody → dragtext
Status: NEW → ASSIGNED
(In reply to comment #3)
> Great, looks like that way you found fixes for some other crashes that
> could appear

Honestly, this is just a dumb port.

> I guess even if we don't take the sWM_FLASHBOUNCEMSG stuff

Of all of it, this seems the most significant.  In the interests of "parallel-ism" with Win32, I'd leave everything in place unless it could be shown to interfere.

> I don't like :: if they are not required, but OK.

I don't either, but fewer lines were changed by adding them than would have been by deleting them.  My goal was stylistic consistency.
Comment on attachment 390740 [details] [diff] [review]
updated OS/2 plugin code

So, as remarked in comment 3 I'll add the #fdef DEBUG on checkin. 
Otherwise this looks OK. Nobody noticed anything bad in the last 4 days, so I'm going to push it.
Attachment #390740 - Flags: review?(mozilla) → review+
Pushed to trunk:
http://hg.mozilla.org/mozilla-central/rev/6121c7853d5d

This should also go to the 1.9.1 branch very soon.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
This is basically the same patch that I checked in to mozilla-central, just slightly updated to fit the 1.9.1 branch.
That patch was obviously broken. This is what will go onto the 1.9.1 branch unless someone objects.
Attachment #392069 - Attachment is obsolete: true
Comment on attachment 392080 [details] [diff] [review]
updated OS/2 plugin code for 1.9.1 branch

Pushed to 1.9.1:
http://hg.mozilla.org/releases/mozilla-1.9.1/rev/4da2a7ffd27f

(too late for FF 3.5.2).
I'll mark this verified, because the code sync has happened, and didn't seem to cause any problems on trunk or branch.
Status: RESOLVED → VERIFIED
Keywords: verified1.9.1
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: