build: 1999040711 platform: win95 expected results: access plug-in page what happens: selecting the link to access a plug-in crashes the app how to reproduce: use optimized build go to: http://slip.mcom.com/projects/marvin/bft/browser/bft_index.html select the link app crashes: APPRUNNER caused an invalid page fault in module RAPTORPLUGIN.DLL at 014f:016f2197. talkback tracking ID DGQO2OVE

I can't test this because slip is down.

I have discovered a bug that might be causing this - what plugin is being loaded?

it's a QT plugin, slip is down at the moment so you won't be able to see the particular test case.

I just fixed a bug that relates to the QT plugin so maybe this is the same problem. I haven't checked it in yet, so I'll test the url when slip comes up.

Fixed on 4.9.99, 2:25PM. Please note that the server has been configured incorrectly and is sending over the incorrect mimetype for the .mov file (it thinks it's of type text/plain instead of movie/quicktime).

This still does not work using 5.0. However, it does display using Communicator 4.6. I am reopening the bug.

Clearing Fixed resolution. Please reset the milestone. M4 is over.

There is config error on the server - I do not think this a problem in the client

If this is server, paw...Invalid bug?

If Alex knows the that the server is not configured correctly than this is an invalid bub

regardless of how the server is configured, we shouldn't crash should we? moving this off to m8 to figure that out.

No longer crashes in the lastest couple of builds of M7.

Did you use optimized build?

No, it was the debug build.

Original report says optimized. Sometimes it happens when app crashes when built release and doesn't if checked. Could you please try it with release build to be absolutely sure?

Tested on the Seamonkey release build 6/17 and it did not crash. However, it still does not work, that is, the plugin does not start. I can write a new bug for this behavior if you wish.

My system hung while writing the message. So I'll repost so you can read the message. Tested on the Seamonkey release build 6/17 and it did not crash. However, it still does not work, that is, the plugin does not start. I can write a new bug for this behavior if you wish.

I think this would be appropriate

Bug #9211 filed for the remaining issue. Closing this one.

Verified in build 1999111520-M11