Description of problem: I was trying to browse Google+ using Epiphny (GNOME Web) and when it loaded the browser hung up and refused to scroll up or down then crashed. This screenshot had been taken right before the crash: http://i.imgur.com/w6Yop4i.png Version-Release number of selected component: epiphany-runtime-3.16.1-1.fc22 Additional info: reporter: libreport-2.6.0 backtrace_rating: 4 cmdline: epiphany crash_function: check_correctness executable: /usr/bin/epiphany global_pid: 5155 kernel: 4.0.5-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 check_correctness at gtkcssstaticstyle.c:216 #5 gtk_css_static_style_new_update at gtkcssstaticstyle.c:271 #6 update_properties at gtkstylecontext.c:824 #7 _gtk_style_context_validate at gtkstylecontext.c:3050 #14 gtk_container_idle_sizer at gtkcontainer.c:1856 #15 _g_closure_invoke_va at gclosure.c:831 #17 g_signal_emit_by_name at gsignal.c:3401 #18 gdk_frame_clock_paint_idle at gdkframeclockidle.c:408 #24 g_main_context_iteration at gmain.c:3869 #25 g_application_run at gapplication.c:2308
Created attachment 1042017 [details] File: backtrace
Created attachment 1042018 [details] File: cgroup
Created attachment 1042019 [details] File: core_backtrace
Created attachment 1042020 [details] File: dso_list
Created attachment 1042021 [details] File: environ
Created attachment 1042022 [details] File: limits
Created attachment 1042023 [details] File: maps
Created attachment 1042024 [details] File: mountinfo
Created attachment 1042025 [details] File: namespaces
Created attachment 1042026 [details] File: open_fds
Created attachment 1042027 [details] File: proc_pid_status
Created attachment 1042028 [details] File: var_log_messages
Created attachment 1042029 [details] File: Screenshot from 2015-06-22 23-18-47.png
Created attachment 1042030 [details] File: screencast-06-22-2015-11:34:32 PM.webm
Created attachment 1042031 [details] File: screencast-06-22-2015-11:36:03 PM.webm
Hmmmm, you hit one of the assertions added to help debug bug #1156124. Interesting. Thanks! *** This bug has been marked as a duplicate of bug 1156124 ***