Bug 280858 - Konqueror crashes
Summary: Konqueror crashes
Status: RESOLVED UPSTREAM
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.7.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-26 22:41 UTC by matbhm
Modified: 2011-12-13 10:30 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description matbhm 2011-08-26 22:41:51 UTC
Application: konqueror (4.7.00 (4.7.0))
KDE Platform Version: 4.7.00 (4.7.0)
Qt Version: 4.7.3
Operating System: Linux 2.6.37.6-0.7-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
Konqueror crashes, when opening some Websites with flash-animation (very often the Websites from www.zeit.de or www.tagesspiegel.de.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Konqueror (kdeinit4), signal: Aborted
[Current thread is 1 (Thread 0x7f7d45d76760 (LWP 3892))]

Thread 6 (Thread 0x7f7d2771d700 (LWP 3985)):
#0  0x00007f7d4467f38c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f7d3a7e91d4 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4
#2  0x00007f7d3690d56c in ?? () from /usr/lib64/libGL.so.1
#3  0x00007f7d4467aa3f in start_thread () from /lib64/libpthread.so.0
#4  0x00007f7d4343067d in clone () from /lib64/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 5 (Thread 0x7f7d0b489700 (LWP 11294)):
#0  0x00007f7d4467f38c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f7d24be9cfc in ?? () from /usr/lib64/browser-plugins/libflashplayer.so
#2  0x00007f7d24d07fd0 in ?? () from /usr/lib64/browser-plugins/libflashplayer.so
#3  0x00007f7d24be9f5c in ?? () from /usr/lib64/browser-plugins/libflashplayer.so
#4  0x00007f7d24bea3ae in ?? () from /usr/lib64/browser-plugins/libflashplayer.so
#5  0x00007f7d3690d56c in ?? () from /usr/lib64/libGL.so.1
#6  0x00007f7d4467aa3f in start_thread () from /lib64/libpthread.so.0
#7  0x00007f7d4343067d in clone () from /lib64/libc.so.6
#8  0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f7d0ac88700 (LWP 11295)):
#0  0x00007f7d4467f38c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f7d24be9cfc in ?? () from /usr/lib64/browser-plugins/libflashplayer.so
#2  0x00007f7d24d07fd0 in ?? () from /usr/lib64/browser-plugins/libflashplayer.so
#3  0x00007f7d24be9f5c in ?? () from /usr/lib64/browser-plugins/libflashplayer.so
#4  0x00007f7d24bea3ae in ?? () from /usr/lib64/browser-plugins/libflashplayer.so
#5  0x00007f7d3690d56c in ?? () from /usr/lib64/libGL.so.1
#6  0x00007f7d4467aa3f in start_thread () from /lib64/libpthread.so.0
#7  0x00007f7d4343067d in clone () from /lib64/libc.so.6
#8  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f7d07c84700 (LWP 11460)):
#0  0x00007f7d4467f6f9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f7d24be9cd1 in ?? () from /usr/lib64/browser-plugins/libflashplayer.so
#2  0x00007f7d24c0b5ed in ?? () from /usr/lib64/browser-plugins/libflashplayer.so
#3  0x00007f7d24be9f5c in ?? () from /usr/lib64/browser-plugins/libflashplayer.so
#4  0x00007f7d24bea3ae in ?? () from /usr/lib64/browser-plugins/libflashplayer.so
#5  0x00007f7d3690d56c in ?? () from /usr/lib64/libGL.so.1
#6  0x00007f7d4467aa3f in start_thread () from /lib64/libpthread.so.0
#7  0x00007f7d4343067d in clone () from /lib64/libc.so.6
#8  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f7d125d4700 (LWP 20596)):
[KCrash Handler]
#6  0x00007f7d4338fab5 in raise () from /lib64/libc.so.6
#7  0x00007f7d43390fb6 in abort () from /lib64/libc.so.6
#8  0x00007f7d4028a74a in g_logv () from /lib64/libglib-2.0.so.0
#9  0x00007f7d4028a7d3 in g_log () from /lib64/libglib-2.0.so.0
#10 0x00007f7d4027e032 in ?? () from /lib64/libglib-2.0.so.0
#11 0x00007f7d4027e3f9 in g_main_context_new () from /lib64/libglib-2.0.so.0
#12 0x00007f7d44a1f3e1 in QEventDispatcherGlibPrivate::QEventDispatcherGlibPrivate (this=0xd85b70, context=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:310
#13 0x00007f7d44a1f4c0 in QEventDispatcherGlib::QEventDispatcherGlib (this=0x10e51b0, parent=0x0) at kernel/qeventdispatcher_glib.cpp:357
#14 0x00007f7d4490a86c in QThreadPrivate::createEventDispatcher (data=0x106d2c0) at thread/qthread_unix.cpp:261
#15 0x00007f7d4490b466 in QThreadPrivate::start (arg=0x106d140) at thread/qthread_unix.cpp:313
#16 0x00007f7d3690d56c in ?? () from /usr/lib64/libGL.so.1
#17 0x00007f7d4467aa3f in start_thread () from /lib64/libpthread.so.0
#18 0x00007f7d4343067d in clone () from /lib64/libc.so.6
#19 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f7d45d76760 (LWP 3892)):
#0  0x00007f7d43427503 in poll () from /lib64/libc.so.6
#1  0x00007f7d4139fc2a in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007f7d413a01a3 in ?? () from /usr/lib64/libxcb.so.1
#3  0x00007f7d413a0234 in xcb_writev () from /usr/lib64/libxcb.so.1
#4  0x00007f7d45246cc6 in _XSend () from /usr/lib64/libX11.so.6
#5  0x00007f7d45247207 in _XReply () from /usr/lib64/libX11.so.6
#6  0x00007f7d4524453d in XTranslateCoordinates () from /usr/lib64/libX11.so.6
#7  0x00007f7d43c3173e in QWidget::mapFromGlobal (this=<value optimized out>, pos=<value optimized out>) at kernel/qwidget_x11.cpp:1327
#8  0x00007f7d43c3179a in QWidget::mapFromGlobal (this=0x1750910, pos=...) at kernel/qwidget_x11.cpp:1320
#9  0x00007f7d43c3179a in QWidget::mapFromGlobal (this=0x175e680, pos=...) at kernel/qwidget_x11.cpp:1320
#10 0x00007f7d43c3179a in QWidget::mapFromGlobal (this=0x17627f0, pos=...) at kernel/qwidget_x11.cpp:1320
#11 0x00007f7d43c3179a in QWidget::mapFromGlobal (this=0x1770990, pos=...) at kernel/qwidget_x11.cpp:1320
#12 0x00007f7d43c3179a in QWidget::mapFromGlobal (this=0x1770cf0, pos=...) at kernel/qwidget_x11.cpp:1320
#13 0x00007f7d43ba70e0 in QApplication::notify (this=<value optimized out>, receiver=0x1770cf0, e=0x7fff7a97ff60) at kernel/qapplication.cpp:4043
#14 0x00007f7d4577fad6 in KApplication::notify (this=0x7fff7a980e30, receiver=0x1770cf0, event=0x7fff7a97ff60) at /usr/src/debug/kdelibs-4.7.0/kdeui/kernel/kapplication.cpp:311
#15 0x00007f7d449f483c in QCoreApplication::notifyInternal (this=0x7fff7a980e30, receiver=0x1770cf0, event=0x7fff7a97ff60) at kernel/qcoreapplication.cpp:731
#16 0x00007f7d43b9f235 in sendEvent (receiver=0x1770cf0, event=0x7fff7a97ff60, alienWidget=0x1770cf0, nativeWidget=0x1095370, buttonDown=0x7f7d44671198, lastMouseReceiver=..., spontaneous=true) at ../../src/corelib/kernel/qcoreapplication.h:215
#17 QApplicationPrivate::sendMouseEvent (receiver=0x1770cf0, event=0x7fff7a97ff60, alienWidget=0x1770cf0, nativeWidget=0x1095370, buttonDown=0x7f7d44671198, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3122
#18 0x00007f7d43c1dc28 in QETWidget::translateMouseEvent (this=0x1095370, event=<value optimized out>) at kernel/qapplication_x11.cpp:4461
#19 0x00007f7d43c1c2e9 in QApplication::x11ProcessEvent (this=0x7fff7a980e30, event=0x7fff7a9808c0) at kernel/qapplication_x11.cpp:3587
#20 0x00007f7d43c44222 in x11EventSourceDispatch (s=0x6fdfa0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#21 0x00007f7d402817d3 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#22 0x00007f7d40281fb0 in ?? () from /lib64/libglib-2.0.so.0
#23 0x00007f7d40282250 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#24 0x00007f7d44a1f60f in QEventDispatcherGlib::processEvents (this=0x617cf0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#25 0x00007f7d43c43ebe in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#26 0x00007f7d449f3c92 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#27 0x00007f7d449f3ea5 in QEventLoop::exec (this=0x7fff7a980be0, flags=...) at kernel/qeventloop.cpp:201
#28 0x00007f7d449f82eb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#29 0x00007f7d32d6c372 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kde-baseapps-4.7.0/konqueror/src/konqmain.cpp:227
#30 0x0000000000407279 in launch (argc=2, _name=0x6c6268 "/usr/bin/konqueror", args=<value optimized out>, cwd=0x0, envc=<value optimized out>, envs=<value optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40b40e "0") at /usr/src/debug/kdelibs-4.7.0/kinit/kinit.cpp:734
#31 0x0000000000407dfd in handle_launcher_request (sock=8, who=<value optimized out>) at /usr/src/debug/kdelibs-4.7.0/kinit/kinit.cpp:1226
#32 0x000000000040859a in handle_requests (waitForPid=<value optimized out>) at /usr/src/debug/kdelibs-4.7.0/kinit/kinit.cpp:1419
#33 0x00000000004091f0 in main (argc=4, argv=0x7fff7a982798, envp=0x7fff7a9827c0) at /usr/src/debug/kdelibs-4.7.0/kinit/kinit.cpp:1907

Possible duplicates by query: bug 280218, bug 280118, bug 279796.

Reported using DrKonqi
Comment 1 Gérard Talbot (no longer involved) 2011-08-28 00:43:09 UTC
> Websites with flash-animation

Are you using Adobe Flash plugin? Eg. You could be using SWF Gnash.

Which version of Flash do you use?

These are 2 important pieces of information to provide in this bug report.

Also, is the crash occuring while using KHTML rendering engine? or webkit rendering engine?

Gérard
Comment 2 Gérard Talbot (no longer involved) 2011-08-28 01:10:42 UTC
This could be a DUPLICATE of bug 273323.

matbhm, always try to provide useful details, helpful specific in bug report. Example given: for this bug report, the bug summary should mention flash, which type (adobe or gnash) and which version. This helps QA, triaging and developers.

I recommend you consult

Investigating Konqueror Bugs
http://www.konqueror.org/investigatebug/

regards, Gérard
Comment 3 matbhm 2011-08-28 06:26:00 UTC
I'm sorry, but my English is crazy! I'm using webkit, khtml is terrible! You can't use it! I use not gnash, gnash is'nt installed. I use flashplayer, the 64-bit-version from adobe-lab. It's the actually version!

Greetings from Berlin, Germany.

-----Ursprüngliche Nachricht-----
Von: bugzilla_noreply@kde.org [mailto:bugzilla_noreply@kde.org] Im Auftrag von Gérard Talbot 
Gesendet: Sonntag, 28. August 2011 02:43
An: matthias.boehme@m-boehme.de
Betreff: [Bug 280858] Konqueror crashes

https://bugs.kde.org/show_bug.cgi?id=280858


Gérard Talbot <browserbugs@gtalbot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |browserbugs@gtalbot.org




--- Comment #1 from Gérard Talbot <browserbugs gtalbot org>  2011-08-28 00:43:09 ---
> Websites with flash-animation

Are you using Adobe Flash plugin? Eg. You could be using SWF Gnash.

Which version of Flash do you use?

These are 2 important pieces of information to provide in this bug report.

Also, is the crash occuring while using KHTML rendering engine? or webkit
rendering engine?

Gérard
Comment 4 Gérard Talbot (no longer involved) 2011-08-28 19:22:05 UTC
Matthias,

I went to 
http://get.adobe.com/de/flashplayer/
then saw the 64-bits link  
( http://labs.adobe.com/technologies/flashplayer10/square/ ) 
which is actually redirected to their flashplayer version 11 beta 2 when clicked
 ( http://labs.adobe.com/technologies/flashplatformruntimes/flashplayer11/ )
So, chances are you are using Flashplayer plugin version 11 beta 2 (and not version 10.3.183.7). You could be sure of this by examining the version in KPackageKit (search flash string and right-click to select display version info).

Matthias, can you edit the bug summary to reflect those useful details:

Edit "Konqueror crashes" 
to
"Flash animated websites (www.zeit.de) often crash: using Adobe Flash player 11 beta 2"

Since Product is Konqueror and since Severity is crash, then those info are not really useful in bug summary field but names of websites and Flash player 11 beta 2 are useful info.

regards, Gérard


> Greetings from Berlin, Germany.
> 
> -----Ursprüngliche Nachricht-----
> Von: bugzilla_noreply@kde.org [mailto:bugzilla_noreply@kde.org] Im Auftrag von
> Gérard Talbot 
> Gesendet: Sonntag, 28. August 2011 02:43
> An: matthias.boehme@m-boehme.de
> Betreff: [Bug 280858] Konqueror crashes
> 
> https://bugs.kde.org/show_bug.cgi?id=280858
> 
> 
> Gérard Talbot <browserbugs@gtalbot.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |browserbugs@gtalbot.org
> 
> 
> 
> 
> --- Comment #1 from Gérard Talbot <browserbugs gtalbot org>  2011-08-28
> 00:43:09 ---
> > Websites with flash-animation
> 
> Are you using Adobe Flash plugin? Eg. You could be using SWF Gnash.
> 
> Which version of Flash do you use?
> 
> These are 2 important pieces of information to provide in this bug report.
> 
> Also, is the crash occuring while using KHTML rendering engine? or webkit
> rendering engine?
> 
> Gérard
Comment 5 Gérard Talbot (no longer involved) 2011-08-28 19:36:15 UTC
Matthias,

I went to 
http://www.zeit.de/index
then clicked on the 
ZDF-NACHRICHTEN IN 100 SEKUNDEN video and did not crash.

The related markup code (only markup; CSS is not available) is:

<div id="player0" class="zol_video inf_wide vid70186496001"><div style="display: block;" class="title dyn_title">ZDF-Nachrichten in 100 Sekunden</div><object id="vid70186496001" name="vid70186496001" data="http://c.brightcove.com/services/viewer/federated_f9?playerID=71289488001&amp;isVid=1&amp;isUI=1&amp;videoSmoothing=true&amp;%40videoPlayer=70186496001&amp;width=370&amp;height=207&amp;linkBaseURL=http://video.zeit.de/video/70186496001&amp;publisherID=18140073001&amp;cacheAMFURL=http%3A%2F%2Fservices.brightcove.com%2Fservices%2Fmessagebroker%2Famf&amp;additionalAdTargetingParams=%3Bbanner-channel%3Dzeit%2Fhomepage%2Fvid&amp;autoStart=false&amp;bgcolor=%23FFFFFF" type="application/x-shockwave-flash" height="207" width="370"><param name="allowfullscreen" value="true"><param name="allowscriptaccess" value="always"><param name="quality" value="high"><param name="wmode" value="transparent"><param name="allowFullScreen" value="true"><param name="linkBaseURL" value="http://video.zeit.de/video/70186496001"><param name="flashvars" value="allowFullScreen=true&amp;linkBaseURL=http://video.zeit.de/video/70186496001"></object><div style="display: block;" class="caption dyn_caption">ZDF-Nachrichten in 100 Sekunden</div></div>

I am using
KDE Platform Version: 4.7.0
Konqueror version: 4.7.0 (KHTML rendering engine)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-11-generic-pae i686 (32bits)
Distribution: Kubuntu 11.04
Adobe Flash player version: 10.3.183.7
here.

I am trying a few video at http://video.zeit.de/index right now ..

Gérard
Comment 6 Gérard Talbot (no longer involved) 2011-08-28 19:52:31 UTC
http://video.zeit.de/video/1132215501001#autoplay

The video loaded and was able to view it entirely.

They use jquery 1.4.2 min.js for their ajax stuff and it has javascript errors: by itself and of itself, this should be investigated. It may not be related to Konqueror crashes but it's not 100% certain.

<script type="text/javascript">
			// <![CDATA[
			!window.jQuery && document.write('<script src="http://scripts.zeit.de/static/js/jquery/1.4.2/jquery-1.4.2.min.js"><\/script>')
			// ]]>
		</script>

and once loaded, Konqueror javascript debugger reports an error at line 90 [Object DOMException]


<link rel="video_src" href="http://c.brightcove.com/services/viewer/federated_f9/71239018001?isVid=1&isUI=1&publisherID=18140073001&playerID=71239018001&domain=embed&videoId=1132215501001"/>
<meta name="video_width" content="460" />
<meta name="video_height" content="260" />
<meta name="video_type" content="application/x-shockwave-flash" />

Those sites like "zeit online" rely on heavily coded javascript like jquery, dynamically writing code with document.write() for various reasons (ajax, advertisements dynamically added) and they generally over-code and over-declare CSS, javascript and HTML.

Gérard
Comment 7 Gérard Talbot (no longer involved) 2011-08-29 00:18:19 UTC
Matthias,

KDE/KHTML developers do not maintain, update or fix webkit rendering engine; webkit ( https://bugs.webkit.org/ ) does.

KDE developers do not maintain, update or fix Adobe Flash plugin (version 10.3 or 11 beta 2); Adobe corporation does.

KDE developers do not maintain, update or fix jQuery javascript library; http://jquery.com/ does. It is not even clear that jQuery is ECMAScript 3, 5.0 or 5.1 compliant to begin with.

So, there is high chances/probabilities that this bug is not fixable by KDE/KHTML developers. It is still possible that the crash bug you experiment may be dependent or caused by Konqueror but it is not likely in my opinion. Chances are low.

All I can tell you with a 100% certainty is that I can view the videos at www.zeit.de while using Konqueror 4.7.0 on the KDE 4.7.0 platform, Qt 4.7.2, and Adobe Flash player 10.3.183.7 . 

ZietOnline uses external content providers ( brightcove.com/services ) for their videos: that too could be another issue although not likely. 

ZietOnline does not create flawless markup code either: they over-code unneedlessly, over-declare, over-qualify, over-style too, over-link (for advertisements). They try to cater for iPad and other media via CSS3 media queries. They over-excessively rely on document.write() without, it seems, opening and closing document stream written dynamically 
http://www.w3.org/TR/DOM-Level-2-HTML/html.html#ID-98948567 

Once Adobe releases a final (stable) version 11 for 64-bits Linux of its Flash plugin, then try it and revisit this bug to update the status of the bug.

regards, Gérard
Comment 8 matbhm 2011-08-29 02:24:20 UTC
Thanks a lot for your answer! But sorry, I have the same problems more often under khtml! And it's not only www.zeit.de or www.tagesspiegel.de, it's also, but not so often, www.focus.de, www.morgenpost.de, www.spiegel.de and many other Websites. 

And a comment to khtml: Try, to open www.nytimes.com. If you scroll down the website, you see a link to videos. Under khtml you see only the MainVideo. The four windows under the MainVideo with alternate videos you don't see!?! With webkit I can see the other Windows with alternate Videos (I'am sorry, but my English is terrible).

I prefer konqueror as Browser, because it is the Browser from KDE. But, sorry, I don't understand, why it is impossible, that this Browser give me the same function without any Problems as other Browser like firefox, Opera, google chrome and others. What the hell is the matter? The same libflash.so, which crashes konqueror, doesn't crashes Firefox, Opera, Google-Chrome and so on! Since more than ten years the konqueror is a big problem. It is the reason, that the great Distributions doesn't use the konqueror! Why, damned, the Konqueror-Team can't do the same like the teams from Firefox, Opera, Chrome and so on? And is KHTML like a religion for the Develop-Team? When KHTML doesn't bring me the function for a good functionable Browser, put it into the trash and forget it!

Greetings from Berlin in Germany,

Matthias.

-----Ursprüngliche Nachricht-----
Von: bugzilla_noreply@kde.org [mailto:bugzilla_noreply@kde.org] Im Auftrag von Gérard Talbot 
Gesendet: Montag, 29. August 2011 02:18
An: matthias.boehme@m-boehme.de
Betreff: [Bug 280858] Konqueror crashes

https://bugs.kde.org/show_bug.cgi?id=280858





--- Comment #7 from Gérard Talbot <browserbugs gtalbot org>  2011-08-29 00:18:19 ---
Matthias,

KDE/KHTML developers do not maintain, update or fix webkit rendering engine;
webkit ( https://bugs.webkit.org/ ) does.

KDE developers do not maintain, update or fix Adobe Flash plugin (version 10.3
or 11 beta 2); Adobe corporation does.

KDE developers do not maintain, update or fix jQuery javascript library;
http://jquery.com/ does. It is not even clear that jQuery is ECMAScript 3, 5.0
or 5.1 compliant to begin with.

So, there is high chances/probabilities that this bug is not fixable by
KDE/KHTML developers. It is still possible that the crash bug you experiment
may be dependent or caused by Konqueror but it is not likely in my opinion.
Chances are low.

All I can tell you with a 100% certainty is that I can view the videos at
www.zeit.de while using Konqueror 4.7.0 on the KDE 4.7.0 platform, Qt 4.7.2,
and Adobe Flash player 10.3.183.7 . 

ZietOnline uses external content providers ( brightcove.com/services ) for
their videos: that too could be another issue although not likely. 

ZietOnline does not create flawless markup code either: they over-code
unneedlessly, over-declare, over-qualify, over-style too, over-link (for
advertisements). They try to cater for iPad and other media via CSS3 media
queries. They over-excessively rely on document.write() without, it seems,
opening and closing document stream written dynamically 
http://www.w3.org/TR/DOM-Level-2-HTML/html.html#ID-98948567 

Once Adobe releases a final (stable) version 11 for 64-bits Linux of its Flash
plugin, then try it and revisit this bug to update the status of the bug.

regards, Gérard
Comment 9 matbhm 2011-08-29 02:38:14 UTC
Dear Gérard,

I use the beta-Version of the flash-Player (64-bit). But there are no Problems with all other Browser (under Linux and under Win7)!

-----Ursprüngliche Nachricht-----
Von: bugzilla_noreply@kde.org [mailto:bugzilla_noreply@kde.org] Im Auftrag von Gérard Talbot 
Gesendet: Montag, 29. August 2011 02:18
An: matthias.boehme@m-boehme.de
Betreff: [Bug 280858] Konqueror crashes

https://bugs.kde.org/show_bug.cgi?id=280858





--- Comment #7 from Gérard Talbot <browserbugs gtalbot org>  2011-08-29 00:18:19 ---
Matthias,

KDE/KHTML developers do not maintain, update or fix webkit rendering engine;
webkit ( https://bugs.webkit.org/ ) does.

KDE developers do not maintain, update or fix Adobe Flash plugin (version 10.3
or 11 beta 2); Adobe corporation does.

KDE developers do not maintain, update or fix jQuery javascript library;
http://jquery.com/ does. It is not even clear that jQuery is ECMAScript 3, 5.0
or 5.1 compliant to begin with.

So, there is high chances/probabilities that this bug is not fixable by
KDE/KHTML developers. It is still possible that the crash bug you experiment
may be dependent or caused by Konqueror but it is not likely in my opinion.
Chances are low.

All I can tell you with a 100% certainty is that I can view the videos at
www.zeit.de while using Konqueror 4.7.0 on the KDE 4.7.0 platform, Qt 4.7.2,
and Adobe Flash player 10.3.183.7 . 

ZietOnline uses external content providers ( brightcove.com/services ) for
their videos: that too could be another issue although not likely. 

ZietOnline does not create flawless markup code either: they over-code
unneedlessly, over-declare, over-qualify, over-style too, over-link (for
advertisements). They try to cater for iPad and other media via CSS3 media
queries. They over-excessively rely on document.write() without, it seems,
opening and closing document stream written dynamically 
http://www.w3.org/TR/DOM-Level-2-HTML/html.html#ID-98948567 

Once Adobe releases a final (stable) version 11 for 64-bits Linux of its Flash
plugin, then try it and revisit this bug to update the status of the bug.

regards, Gérard
Comment 10 Gérard Talbot (no longer involved) 2011-08-29 04:10:40 UTC
(In reply to comment #8)
> it's not only www.zeit.de or www.tagesspiegel.de, it's also,
> but not so often, www.focus.de, www.morgenpost.de, www.spiegel.de and many
> other Websites. 
> 
> And a comment to khtml: Try, to open www.nytimes.com. 


You make the same error that many people do: they mention a lot of sites but at bugs.kde.org we can not work that way. Every single website has its own HTML code, it own CSS code, own flash-related code, javascript code, ajax code, etc.. We can not, just like that, deal with a bug report that lists many websites. Basically, we want to deal with one single, defined, accurately targeted known issue per bug report. Only one. And a reduced testcase is the most preferred way to deal with bug report.

Many of those sites have bad code, bloated code, external service content added dynamically. We need clear testcases, clean testcases, reduced testcases. Listing websites is not like listing code. And listing code is not like creating a reduced testcase.

"
due to the large number of bug reports received, and the large amount of time that it takes developers to identify issues, reports which do not include a testcase or are not described in reproduceable steps will get a low priority of fixing.
(...)
follow these steps to build a test case:

Save the relevant page or frame on your disk.
Load the page from your disk and see if the problem is still there.
Only if it's necessary to reproduce the bug: save framesets, images etc.
Throw out anything that has nothing to do with the bug, i.e. delete some stuff, reload to check if the problem is still there, delete more stuff. Do this until you found the exact cause of the problem. The HTML file should not have more than 20 lines at the end.
The important part is: the page should be as short as possible to be able to still reproduce the bug. The shorter it is, the sooner it will get fixed!
"
Investigating Konqueror Bugs (I already mentioned that page)
http://www.konqueror.org/investigatebug/



Many other browser manufacturers also ask people to submit bug reports where a reduced testcase can be done out of these.

Mozilla:
How to Really, Really Help Developers on Bugs -- Minimal Testcases
https://wiki.mozilla.org/MozillaQualityAssurance:Triage#How_to_Really.2C_Really_Help_Developers_on_Bugs_--_Minimal_Testcases



Webkit: 
"
If you have created a test case reduction for the bug, please add it to the bug report as an attachment rather than putting it on a web server and listing its URL here. Doing so makes it easier to work on the bug, and can be a first step towards checking in the test case along with the bug fix.
"
Bug Reporting Guidelines
http://www.webkit.org/quality/bugwriting.html


Test Case Reduction (webkit)
A general guide to test case reduction
http://www.webkit.org/quality/reduction.html


> If you scroll down the
> website, you see a link to videos. Under khtml you see only the MainVideo. The
> four windows under the MainVideo with alternate videos you don't see!?! 

Then that would require another bug report. With 1 (not more than 1) defined webpage, you can file 1 bug report. No more than 1 defined webpage per bug report. Websites do not have, do not share the same markup, CSS, javascript, ajax, etc. code and they very often have well-formedness, validation, compliance errors.

The www.zeit.de and www.tagesspiegel.de have thousands of lines of code! We want to deal with minimal testcases which have no more than 50 lines of code. The shorter, the better.


> I prefer konqueror as Browser, because it is the Browser from KDE. But, sorry,
> I don't understand, why it is impossible, that this Browser give me the same
> function without any Problems as other Browser like firefox, Opera, google
> chrome and others. What the hell is the matter? 

Be careful here! I used Konqueror 4.7.0 to view zeit.de and had no problems none whatsoever to view videos. And I listed all of my configuration. You use a **beta** flash plugin whereas I do not.


> The same libflash.so, which
> crashes konqueror, doesn't crashes Firefox, Opera, Google-Chrome and so on!
> Since more than ten years the konqueror is a big problem. It is the reason,
> that the great Distributions doesn't use the konqueror! Why, damned, the
> Konqueror-Team can't do the same like the teams from Firefox, Opera, Chrome and
> so on? And is KHTML like a religion for the Develop-Team? When KHTML doesn't
> bring me the function for a good functionable Browser, put it into the trash
> and forget it!

All of the above has nothing to do with a serious bug report. 

Flash plugin used to crash a lot in IE8 and Safari and Chrome. Microsoft, Apple and Google complained publicly about Adobe's flash plugin: this can be verified, confirmed by searching the web.

Nevertheless, again, I am telling you that 
- you are using a beta flash plugin created, maintained by Adobe, not KDE people; flash is not web standard but a proprietary plugin. Adobe may be ignoring any/all browsers which are not IE, Firefox, Chrome, Safari and Opera. Who knows?
- you are using webkit rendering engine created, maintained by webkit, not KDE people

I know that Konqueror using the KHTML rendering engine is not bad but it is not flawless, not perfect.

Gérard
Comment 11 Gérard Talbot (no longer involved) 2011-08-29 04:19:44 UTC
(In reply to comment #9)
> I use the beta-Version of the flash-Player (64-bit). But there are no Problems
> with all other Browser (under Linux and under Win7)!

Matthias, chances are Adobe did not test (or did not test sufficiently) Konqueror with KHTML rendering engine.

The other browsers are IE9 by Microsoft, Firefox 6 by Mozilla, Chrome by Google: they all have a bigger share of the browser market and are own by corporations which dispose of millions or billions of dollars. So, which browser(s) are Adobe going to serve and to test first?

The root, cause of the crashes you experimented on zeit.de is not known for sure. In my experience, these crashes may have nothing or little to do with Konqueror.

Gérard
Comment 12 Gérard Talbot (no longer involved) 2011-08-29 18:03:41 UTC
Matthias,

Do me and yourself a favor! Go to
http://www.adobe.com/software/flash/about/

Do you crash when visiting that webpage?

If you crash when visiting that webpage, then it definitely means that Adobe must be notified of this because you'd be using their plugin on their webpage.
You may also want to try your 64-bits Flash plugin on other test webpages for flash; there must be a few at http://www.adobe.com/software/flash/

Notice that, in that webpage
http://www.adobe.com/software/flash/about/
, they list Mozilla, Firefox, SeaMonkey and Chrome for Linux but they do not make mention of Konqueror! 

regards, Gérard
Comment 13 Gérard Talbot (no longer involved) 2011-08-29 18:24:16 UTC
Matthias,

More things, ideas, possibilities you can do or try.

Visit

https://bugbase.adobe.com/?event=search

and, after creating an account, file a bug for (Search Criteria)

Product : Adobe Flash Player

Version: Flash Player 11

Area: Browser Integration

Platform: Linux

Browser: -

------------

Visit 
How can we help you
http://www.adobe.com/aboutadobe/contact.html

and choose 
"I need help using my software or it does not seem to be working correctly"
from the drop-down list.

And ask them if they tested Konqueror 4.7.0 (KHTML rendering engine) under KDE 4.7.0,  64bits.

In other words, let them tell you that Konqueror has the problem, not Adobe Flash plugin.

There is a reason to suspect they may be causing the issue: I generally have no problem displaying video when using 
KDE Platform Version: 4.7.0
Konqueror version: 4.7.0 (KHTML rendering engine)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-11-generic-pae i686 (32bits)
Distribution: Kubuntu 11.04
Adobe Flash player version: 10.3.183.7

but you do with Adobe Flash player version 11.0 beta 2 with your 64bits system.

Gérard
Comment 14 Gérard Talbot (no longer involved) 2011-08-30 20:45:02 UTC
This bug 280858 could be a DUPLICATE of bug 278180; it has the same description.

Gérard
Comment 15 Gérard Talbot (no longer involved) 2011-08-30 23:26:48 UTC
Matthias,

Worth reading:

Flash Player Help and Support
   Troubleshooting
     Flash Player doesn't work
        64-bit operating systems
http://www.adobe.com/support/flashplayer/


Flash Player | 64-bit operating systems
http://kb2.adobe.com/cps/000/6b3af6c9.html


-------------------


Report a Flash Player crash (to Adobe)
http://kb2.adobe.com/cps/839/cpsid_83975.html

Interestingly, they explain how to create and submit a Flash Player crash log for Windows users but I'm sure this could be done for KDE users. This is where an user like yourself could help the whole Konqueror community (who may be having crash/problems/issues with Flash players), the KDE developers who are generally over-burdened and too few and help yourself to begin with.

-------------------


http://community.adobe.com/help/search.html?searchterm=Konqueror&go=go&q=Konqueror&l=flashplayer_product_adobelr&x=0&y=0&area=0&lr=en_US&hl=en_US

As you can see, Konqueror users can report their issues to Adobe or to other community users.

--------------

You can also file, open a bug report and search existing ones:
Feature Request/Bug Report Form
https://bugbase.adobe.com/

regards, Gérard
Comment 16 Dawit Alemayehu 2011-11-21 19:42:28 UTC
See https://bugs.webkit.org/show_bug.cgi?id=66839.

This is a known problem with 64-bit flash and QtWebKit. The issue seems to be resolved for most people with the latest 11.2 beta version.
Comment 17 Gérard Talbot (no longer involved) 2011-11-22 01:15:03 UTC
Matthias,

If you are still reading this, try to download and install the latest 11.2 beta:
http://get.adobe.com/flashplayer/

Dawit,

Thanks for your involvements into Konqueror crashes bugs and Flash-related issues.

regards, Gérard
Comment 18 nellyaufderinsel 2011-12-13 10:30:36 UTC
Maybe #280858  #288641  #288815  #288862  #288793  

have basically the same problem.

All KDE applications related to http  (Konqueror, Akregator, Kmail, 
Rekonq (Aurora) )  crashes while loading Plugins ( flash, swf, nsplugin, java,
whatever ? ) when WebKit is used.
In KHTML mode, Videos are not playing properly on Konqueror and Akregator.

This problem is no new one. It exist since years ago (KHTML)

In the nearest past ( last 10 Months etc..... ) Konqueror and Akregator works fine !!!
But the last few days it is stronger than ever bevor, Konqueror und Akregator are never usuable.

Refer to #280858  comment #7

this will maybe the right startup-point to insulate this problem.

But sorry, i´am just a longtime Konqi-user. My statement will be only a tip.