Bug 22850 - [Gtk] Flash 10 plugin crashes webkit
Summary: [Gtk] Flash 10 plugin crashes webkit
Alias: None
Product: WebKit
Classification: Unclassified
Component: Plug-ins (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P1 Critical
Assignee: Nobody
URL: http://youtube.com
Depends on:
Reported: 2008-12-14 00:29 PST by Dmitry
Modified: 2010-12-01 17:29 PST (History)
7 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry 2008-12-14 00:29:28 PST
I've installed Flash 10 plugin (.deb package from Adobe site), and webkit from svn crashes with it. Opera 9.52 works fine.

$ WebKitTools/Scripts/run-launcher --qt
Starting webkit launcher with LD_LIBRARY_PATH set to point to built WebKit in /home/krasu/MyProjects/WebKit-svn/WebKitBuild/Release/lib.

(process:18614): Gtk-CRITICAL **: gtk_clipboard_get_for_display: assertion `display != NULL' failed
Adobe Flash Player: gtk_clipboard_get(GDK_SELECTION_PRIMARY); failed. Trying to call gtk_init(0,0);
Segmentation fault
Comment 1 Dmitry 2008-12-14 00:33:20 PST
My system is KUbuntu 8.04.1, glibc 2.7-10ubuntu3, g++ 4.2.4, Qt 3.3.8 and 4.4.3.
Comment 2 Charlie Schloss 2009-04-23 09:29:24 PDT
Here on my Mac 10.4.11 Intel, Flash Player 10 crashes Safari and Opera, could it be a bug in flash player?
Comment 3 Charlie Schloss 2009-04-23 09:34:54 PDT
Flash Player 10 has been crashing Safari 3.2.1 (4525.27.1) and Opera 9.64 (5270) for me, could it be Flash Player 10 (10,0,22,87)

Mac OS 10.4.11 Intel
Comment 4 Harshana 2009-08-20 00:37:04 PDT
Same here on Chrome (Official Build 23222) WebKit 532.0 on WIN XP SP3 Flash Player 10 .
Comment 5 Alexey Proskuryakov 2010-03-14 14:53:53 PDT
This report is about Gtk (Linux) specifically. It is not helpful to report problems on other platforms here.
Comment 6 Dawit A. 2010-09-11 11:53:18 PDT
(In reply to comment #5)
> This report is about Gtk (Linux) specifically. It is not helpful to report problems on other platforms here.

This is not a Gtk problem, but as usual Adobe's fault. See http://webkit.org/b/40567 for the details and the workaround that has already been committed upstream. Please note that the workaround is applicable only for QtWebKit based platforms which is what the original reporter here was using...
Comment 7 Martin Robinson 2010-12-01 17:29:16 PST
This seems to be fixed in the other bug mentioned. Closing.