Bug 39868 - [Qt] Flash plugin crash, when switching to fullscreen mode on Maemo 5 using Qt 4.6.2
Summary: [Qt] Flash plugin crash, when switching to fullscreen mode on Maemo 5 using Q...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Qt (show other bugs)
Version: 528+ (Nightly build)
Hardware: Other Linux
: P2 Normal
Assignee: Nobody
URL: http://bugreports.qt.nokia.com/browse...
Keywords: Qt, QtTriaged
Depends on:
Blocks:
 
Reported: 2010-05-28 02:24 PDT by Dominik Holland
Modified: 2010-07-08 05:05 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dominik Holland 2010-05-28 02:24:12 PDT
The plugin crashes, when you switch to fullscreen mode using QWebView.

Qt-Bug: http://bugreports.qt.nokia.com/browse/QTBUG-11055
Comment 1 Simon Hausmann 2010-06-17 06:09:02 PDT
From the Qt bug report:

. Test application
#include <QtGui>
#include <QtWebKit>
int main(int argc, char * argv[])

{ QApplication app(argc, argv); QWebView view; view.settings()->setAttribute(QWebSettings::PluginsEnabled,true); view.load(QUrl("http://www.youtube.com/watch?v=KMU0tzLwhbE")); view.show(); return app.exec(); }
2. Run it on N900 with 19-1 image installed.
3. Tap on fullscreen button.

Outcome:
Application crashes with a backktrace:
#0 XChangeProperty (dpy=0x0, w=65011921, property=68, type=33, format=32, mode=0, data=0xbeda2c44 "\2", nelements=1) at ../../src/ChProp.c:48
#1 0x42b886d0 in XSetTransientForHint (dpy=0x0, w=65011921, propWindow=1119251380) at ../../src/SetHints.c:286
#2 0x45b6e428 in ?? () from /usr/lib/browser/plugins/libflashplayer.so
#3 0x45b6e428 in ?? () from /usr/lib/browser/plugins/libflashplayer.so

Additional info:
MicroB is using the same flash plugin, but doesn't crash in similar conditions.
Comment 2 Harald Fernengel 2010-07-06 07:59:03 PDT
Note that this seems to be an internal flash player bug, waiting for feedback from Adobe.
Comment 3 Harald Fernengel 2010-07-08 05:03:23 PDT
Turned out not to be a WebKit issue but an issue in the Flash Maemo integration layer. Closing bug.