170518 - crash on http://www.helsinginsanomat.fi

Status: RESOLVED WORKSFORME

(Core Graveyard :: Plug-ins, defect)

Description

[Markus Hübner]

Just visited URL and it crashed.

using trunk build 2002092404 on win-xp pro.

TB11477286W

Comment 1

[David Bradley]

Attachment: Stack for TB incident

Comment 2

[Matthias Versen [:Matti]]

-> plugins (shockwave flash crash)

Comment 3

[rubydoo123]

What version of Flash are you using?

Comment 4

[Markus Hübner]

latest version on win-xp pro.

Comment 5

[shrirang khanzode]

wfm with flash 6.0r47 and winNT

Comment 6

[Matthias Versen [:Matti]]

wfm with a 1 day old trunk and flash 6.0 R47

Comment 7

[rubydoo123]

Well, using the trunk build from today and using npswf32.dll Shockwave Flash 6.0
r47, I do not crash. And I do not see any plug-ins on that page. I see lots of
IFrames, but no plug-ins.

Shrir -- do you see anything?

Comment 8

[Mats Palmgren (inactive)]

*** Bug 170527 has been marked as a duplicate of this bug. ***

Comment 9

[Jerry Baker]

My bug marked as a duplicate. The crash in bug 170527 did not happen with
20020922 build. 

Flash version from about:plugins - Flash 5.0 r41

Comment 10

[rubydoo123]

I finally found an object element, the object is in the iframe:
http://adserver.sanomawsoy.fi/hserver/SITE=HELSINGINSANOMAT/AREA=ETUSIVU.UUTISET/AAMSZ=468x60/PP=1/acc_random=1032891461031?

Rendering that page does not cause a crash for me

Reporter: can you please upgrade to a more current version of Flash, I think the
object may be calling a version of Flash that requires scripting

Comment 11

[Markus Hübner]

using win-xp pro sp1 and Shockwave Flash 5.0 r41 when crashing.

Comment 12

[rubydoo123]

Yes, you need to upgrade your Flash. go here and get the newest version and see
if you still have the issue:
http://www.macromedia.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash&P5_Language=English

Comment 13

[av (gone)]

Attachment: isolated test case

The site uses a technique of JS generation of the alt embed tag inside the
object tag. Reporter, could you please check if you see the crash on this test
case? Also, you might want to try to update Flash to version 6 and see if the
crash is gone.

Comment 14

[Markus Hübner]

using latest version (Shockwave Flash 6.0 r47) I don't crash on the testcase.

Comment 15

[serge (gone)]

Comment on attachment 100425 [details]
isolated test case

>src="http://adimages.sanomawsoy.fi/salonen/oikotie/tyopaikka_468_0235.swf?url=http://swing.sanomawsoy.fi 
there's flash 6 bug 135992, it does escape url after '?', so there will be no
flash content from such src, and therefore no crash.

Comment 16

[Jerry Baker]

Crashing because of having Flash 5 is not acceptable. I am not upgrading to
Flash 6, and have no plans to do so. This is a regression introduced in the last
two days. It shouldn't mean that every Mozilla user on the planet has to upgrade
their Flash in order not to crash.

Comment 17

[Markus Hübner]

Think so too.

Comment 18

[Matthias Versen [:Matti]]

>Crashing because of having Flash 5 is not acceptable
That's wrong. AFAIK the flash plugin crashes and this means that this is a bug
in the plugin.
We don't accept bugs reports from old builds and why should we make a difference
with an old plugin ?

Comment 19

[Peter Lubczynski]

The Gecko plugins team has worked closely with Macromedia to ensure the version
of Flash 6 that comes with Netscape 7 is the most compatible for Mozilla-based
browser. Among one of the fixes is the ability to control it through Javascript.
You can update by clicking here:
ftp://ftp.netscape.com/pub/netscape7/english/7.0/windows/win32/ewc9e/flash.xpi

Comment 20

[rubydoo123]

Closing bug out as WFM, using the the current plug-in from Macromedia resolves
this issue

Comment 21

[Mats Palmgren (inactive)]

Isn't it worth trying to find out what caused this regression?

If this problem remains when Mozilla 1.2 is released many users will see
Mozilla crash within first few minutes of using it. I don't think most users
will care about the explanation above (it's not a Mozilla bug, it's a
plugin bug), because what they see is that Mozilla exits abnormally.
This will of course lead to many unnecessary bug reports too...

If this is a regression in the last 2-3 days then it would be fairly easy to
find out what caused it? and then make a decision if it's worth "fixing".

Comment 22

[Jerry Baker]

This bug didn't exist in 20020924 trunk, but if closing it makes you feel better
go ahead. It doesn't make Mozilla any better, or change the fact that something
that changed in Mozilla in the last two days is causing this.