104218 - flash plug-in handles dynamic content much slower than on IE 5.5

Status: RESOLVED WORKSFORME

(Core Graveyard :: Plug-ins, defect)

Description

[Patrick]

We have a flash application that uses dynamic contents received in the xml
format. This application is 3 to 4 times slower on Mozilla than on IE.

I can't give an example here as it is internal to my job.

Patrick

Comment 1

[av (gone)]

Hm... I wonder if this is related to our constant prefs check on every plugin 
call. You might want to try tomorrow's build.

Comment 2

[Peter Lubczynski]

Today's morning builds should have my changes. Reporter: can you try with an
updated build?

Comment 3

[Patrick]

Tried with build 2001101103. Haven't seem major improvements.

Comment 4

[Peter Lubczynski]

How much memory and how fast is your CPU?

Comment 5

[Patrick]

192MB, PII-300
Of course, both tests are made on the same machine.

Comment 6

[Peter Lubczynski]

Is it all Flash 5 animations or just a specific kind? Could you post a link or
attach a minimal testcase? Do other plugins show this problem?

Comment 7

[Patrick]

AFAIK, it is not an animation except if everything in Flash is animation. It is
a table that is filled in with data and that operation takes 7-8 s with Mozilla
while it takes only 2 s with IE 5.5.

I haven't tested it for any other Flash application or plugin.

I can't provide you with a link or a testcase as it is company confidential
until it is published.

Comment 8

[Peter Lubczynski]

We need at least a testcase in order to reproduce this bug. Could you create and
attach a simplified sample HTML page that still shows this problem without
revealing confidential information?

Comment 9

[Patrick]

I am not a Flash programmer and I doubt the person doing it will have the time
and the will to do it. I will raise the issue on Monday internally (being at
home now) to see if someone volonteers but don't count on it!

Any programmer with knowledge in ActionScript and some concepts of xml should be
able to write a sample.

Isn't Macromedia a partner? It would take ten minutes for one of them to build a
testcase. I am not CC'ing right now because I am not sure it would be the right
persons but it might be the path to follow.

Comment 10

[Sitsofe Wheeler]

Adding qawanted keyword. If we don't have a testcase this one could be tough to
fix...

Comment 11

[Patrick]

I am not sure this is still valid with Flash 6 (my computer is too fast to see
it now) but what I am sure of is that it doesn't work as good as it does with
IE. Just go to http://tones.base.be/htm/fr/home.htm and choose "catégories".
There you will see, immediately or after a while (15-20s) that some logos
disappear. That doesn't occur with IE.

As for the performance, I'll try to test it on a slower PC but if you have the
opportunity to do so, it would be very useful. Comparing flash 5 to flash 6
would be a good idea too.

Comment 12

[Peter Lubczynski]

Does the same happen with Flash 5?

*** This bug has been marked as a duplicate of 132759 ***

Comment 13

[Patrick]

Yes, of course, the same occurs with Flash 5 as it was originally described with
Flash 5. The unknown part is whether this problem is present with Flash 6!

Leaving as duplicate as I don't know if the original problem is still present
while waiting for your answer to the preceeding.

Comment 14

[shrirang khanzode]

i don't see cpu usage go up here...is this really a dup peter?

Comment 15

[Peter Lubczynski]

Reopening based on reporters comments....

I am seeing exactly what is described in comment #11, but you need to look under
"logos". From plugin log, I see URLNotify being called several times, perhaps
there is a bug there.

Reporter: Does this work with Nav 4.x?

Comment 16

[rubydoo123]

hmm, on winXP using the branch build from 20020625 and Flash 6, it takes about
2-3 seconds to load either page

Comment 17

[Patrick]

Sorry, I'm not using nav 4 anymore. I've abandonned it a long time ago.

BTW, I am now on that slower computer and I don't see the issue we had before.
It's true that many things changed since then: Flash version, Mozilla version,
Flash app version and most importantly, the size of the xml files to be
processed by the Flash app. If one wants to try to reproduce this issue, he
should load large xml files.

I think this one may be closed (WFM) unless another situation is found.

What about the other issue? Should we open another bug?

Comment 18

[rubydoo123]

yes, if you see other issues, then please open a bug for each, multiple issues
per one bug is not very helpful for us.

Thanks for looking at this again -- as requested, marking as wfm