Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 522482

Summary: net-libs/webkit-gtk-2.4.4[-r200] - segmentation fault while playing html5 video in sweep_line_delete_edge (edge=0x7fffffff63f0, sweep=0x7fffffff60e0) at .../work/cairo-1.12.16/src/cairo-bentley-ottmann-rectangular.c:558
Product: Gentoo Linux Reporter: Christian Albertsen <christian>
Component: [OLD] GNOMEAssignee: Gentoo Linux Gnome Desktop Team <gnome>
Status: RESOLVED NEEDINFO    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge --info
luakit backtrace

Description Christian Albertsen 2014-09-10 06:37:16 UTC
Created attachment 384510 [details]
emerge --info

I tried it with www-client/luakit www-client/uzbl and www-client/surf:

1. Browse to: http://www.youtube.com/html5 and activate the html5 video player
2. View any youtube video on the youtube site or embedded in any other site.

Most of the time it segfaults while playing the video the browser. Sometimes the video plays to the end, but the next video surely leads to a segfault.

Downloading the video via youtube-dl and viewing it via "gst-launch-1.0 playbin" doesn't crash the browser. chromium also doesn't segfault.
Comment 1 Christian Albertsen 2014-09-10 06:38:31 UTC
Created attachment 384512 [details]
luakit backtrace
Comment 2 Pacho Ramos gentoo-dev 2014-10-04 08:19:57 UTC
Please try with 2.4.6, it solves some html5 crashes per upstream changelog
Comment 3 Christian Albertsen 2014-10-08 19:30:51 UTC
It still crashes for me.
Comment 4 Pacho Ramos gentoo-dev 2014-10-08 20:54:55 UTC
Then, please report this to upstream and paste the backtrace there too -> bugzilla.webkit.org

Maybe that way they will take care of that issue in future versions :/

Thanks
Comment 5 Pacho Ramos gentoo-dev 2014-10-25 11:34:44 UTC
did you report it? :)
Comment 6 Pacho Ramos gentoo-dev 2015-01-13 15:57:31 UTC
(In reply to Pacho Ramos from comment #5)
> did you report it? :)