RESOLVED FIXED 72237
[GTK] Possible crash when destroying after called widgetSizeChanged. 
https://bugs.webkit.org/show_bug.cgi?id=72237
Summary [GTK] Possible crash when destroying after called widgetSizeChanged.
Ryuan Choi
Reported 2011-11-13 20:58:20 PST
It's hardly reproducible. but I got below segmentation fault when killed GtkLauncher. 0xb6b6a25c in WebKit::ChromeClient::paint(WebCore::Timer<WebKit::ChromeClient>*) () from /workspace/webkit/gtk-webkit/WebKitBuild/Release/.libs/libwebkitgtk-3.0.so.0 (gdb) bt #0 0xb6b6a25c in WebKit::ChromeClient::paint(WebCore::Timer<WebKit::ChromeClient>*) () from /workspace/webkit/gtk-webkit/WebKitBuild/Release/.libs/libwebkitgtk-3.0.so.0 #1 0xb6b6a943 in WebKit::repaintEverythingSoonTimeout(WebKit::ChromeClient*) () from /workspace/webkit/gtk-webkit/WebKitBuild/Release/.libs/libwebkitgtk-3.0.so.0 #2 0xb631a92f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb631925f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb6319990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb6319f9b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #6 0xb66bcf95 in gtk_main () from /usr/lib/libgtk-3.so.0 #7 0x08049e23 in main ()
Attachments
Patch (1.55 KB, patch)
2011-11-13 21:02 PST, Ryuan Choi 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Ryuan Choi
Comment 1 2011-11-13 21:02:16 PST
Created attachment 114875 [details] Patch
Martin Robinson
Comment 2 2011-11-14 02:09:38 PST
Comment on attachment 114875 [details] Patch Thanks!
Ryuan Choi
Comment 3 2011-11-14 02:17:18 PST
Comment on attachment 114875 [details] Patch No problem. It's my pleasure to contribute WebKit and WebKitGtk+.
WebKit Review Bot
Comment 4 2011-11-14 03:24:43 PST
Comment on attachment 114875 [details] Patch Clearing flags on attachment: 114875 Committed r100121: <http://trac.webkit.org/changeset/100121>
WebKit Review Bot
Comment 5 2011-11-14 03:24:48 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.