Skip to content
This repository has been archived by the owner on May 10, 2018. It is now read-only.

[Flash] Crash while jumping forward in a YouTube video #1505

Closed
spaeps opened this issue Oct 24, 2014 · 7 comments
Closed

[Flash] Crash while jumping forward in a YouTube video #1505

spaeps opened this issue Oct 24, 2014 · 7 comments

Comments

@spaeps
Copy link
Contributor

spaeps commented Oct 24, 2014

I'm referring an issue reported on the Arch Linux BTS [1].

Qupzilla (Qt5) crashes when jumping forward in a YouTube video,
in a point not already loaded.

The Qt4 build is not affected by this.

Probably related to qt5-webkit since otter-browser (using Qt5)
is affected too.

[1] https://bugs.archlinux.org/task/40151#comment123532

@JHooverman
Copy link
Member

I am able to reproduce this issue with

QupZilla (Application version: 1.9.0 (ce528cf), Qt version: 5.4.0, WebKit version: 538.1)
QtTestBrowser (Qt version: 5.4.0, WebKit version: 538.1)

Since this is a QtWebkit issue it will not be fixed in QupZilla. Thus, I have opened an issue upstream. Maybe you want to have a look at the issue status on QTBUG to close your issue on archlinux as well, once it is fixed upstream.

@spaeps
Copy link
Contributor Author

spaeps commented Oct 28, 2014

This already merged patch solves the issue (that's not included in the 5.4.0 alpha):
https://qt.gitorious.org/qt/qtwebkit/commit/13ebee35e169a8b1210851ec494951815c70620c

@JHooverman
Copy link
Member

@spaeps: Is it safe to close this issue?

@ghost
Copy link

ghost commented Nov 5, 2014

I've been getting crashes watching flash videos on YouTube. I wasn't jumping forward, I was just watching it...

Here's the last video I was watching that generated this crashlog;

http://www.youtube.com/watch?v=grVvOTys3aE

Here's the crashlog;

Time: Tue Nov 4 18:01:46 2014
Qt version: 5.3.2 (compiled with 5.3.2)
QupZilla version: 1.8.4
WebKit version: 538.1

============== BACKTRACE ==============
#0: qupzilla() [0x40367f]
#1: /lib64/libc.so.6(+0x369f0) [0x7f72ad8ea9f0]
#2: /usr/lib64/libQt5WebKit.so.5(+0x9b9ddc) [0x7f72b1631ddc]
#3: /usr/lib64/libQt5WebKit.so.5(+0x9b7370) [0x7f72b162f370]
#4: /usr/lib64/libQt5WebKit.so.5(+0x9b937c) [0x7f72b163137c]
#5: /usr/lib64/libQt5Core.so.5(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x756) [0x7f72aeca8216]
#6: /usr/lib64/libQt5Network.so.5(+0x84892) [0x7f72af844892]
#7: /usr/lib64/libQt5Network.so.5(+0x104d7b) [0x7f72af8c4d7b]
#8: /usr/lib64/libQt5Core.so.5(_ZN7QObject5eventEP6QEvent+0x276) [0x7f72aeca8eb6]
#9: /usr/lib64/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x8c) [0x7f72b05907dc]
#10: /usr/lib64/libQt5Widgets.so.5(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x416) [0x7f72b0595716]
#11: /usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x65) [0x7f72aec79025]
#12: /usr/lib64/libQt5Core.so.5(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1e7) [0x7f72aec7ae77]
#13: /usr/lib64/libQt5Core.so.5(+0x2cf6c3) [0x7f72aecd06c3]
#14: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x146) [0x7f72aae07316]
#15: /usr/lib64/libglib-2.0.so.0(+0x47668) [0x7f72aae07668]
#16: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f72aae0770c]
#17: /usr/lib64/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5c) [0x7f72aeccfb3c]
#18: /usr/lib64/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x11b) [0x7f72aec76f3b]
#19: /usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication4execEv+0x86) [0x7f72aec7e566]
#20: qupzilla() [0x402ceb]
#21: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f72ad8d5d05]
#22: qupzilla() [0x403035]

QupZilla just crashed when I went to speedtest.net.

Seems like there's a lot of crashes going on related to flash...

@JHooverman
Copy link
Member

This issue is fixed upstream, but as far as I understood, the solution will be in 5.4.0 RC. They do not plan a version 5.3.3.

@ghost
Copy link

ghost commented Nov 5, 2014

Ok...

@JHooverman
Copy link
Member

Please update your QtWebkit as this issue does not longer happen with the latest version.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants