Bug 36363 – [Qt] Page loads slow with media elements

• Status: RESOLVED
• Resolution: WONTFIX
• Component: Media

[Casper van Donderen]

Created attachment 51153 [details]
Testcase showing slow loading of audio element

The page in the attachment loads really slow when the media element is included.

It seems as though the autobuffer property is automatically set, the file immediately begins to play after clicking the image.
The page loads instantaneously in the QtLauncher when the audio element is commented out.

This behaviour did not occur in a nightly build from 15 March.

Using Qt 2010.01 MinGW.

[Simon Hausmann]

(In reply to comment #0)
> This behaviour did not occur in a nightly build from 15 March.

Oh, do you mean that this is a regression since March 15th in the trunk?

[Casper van Donderen]

Yes, it is a regression.

I could not find any changes in the media player code.

[Simon Hausmann]

(In reply to comment #2)
> Yes, it is a regression.
> 
> I could not find any changes in the media player code.

Hmm, March 15th is not too far back. Could you do a bi-section and find out which change caused it? :)

[Casper van Donderen]

Tor Arne told me to look in the WebCore/platform/graphics/MediaPlayer* and WebCore/platform/graphics/qt/MediaPlayer* files.

There is nothing special happening there and I'm not familiar enough with the codebase to know where else to look.

[Jocelyn Turcotte]

In Qt 4.7 with MinGW I got a friendly crash instead.
Reported there: http://bugreports.nokia.troll.no/browse/QTBUG-10221

Since you are using Qt 4.6 with MinGW which uses phonon, I guess that these two problems are unrelated.

For me it worked as expected in Qt 4.6 and in Qt 4.7 with MSVC so I couldn't reproduce your problem.

[Jocelyn Turcotte]

As discussed with Casper the slow loading is around 2 seconds on a desktop computer and happens only the first time the page is loaded.

This is down to around 0.5 seconds with 4.7 so it is probably linked to the phonon initialization.

If, after testing, the delay is quite longer when loading on a smaller device, this would be more critical.

I'll close it as won't fix for now.