Bug 198470

Summary:	nspluginviewer brings the system / X.org completely down to crawl
Product:	[Applications] konqueror	Reporter:	Diederik van der Boor <vdboor>
Component:	nspluginviewer	Assignee:	Konqueror Developers <konq-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	finex
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Diederik van der Boor 2009-07-01 00:05:30 UTC

Version:           onbekend (using 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)) "release 138", KDE:KDE4:Factory:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (i686) release 2.6.30-48-pae

For some reason, nspluginviewer completely brings down my system performance to almost totally freeze.

This happens with:
- open konqueror
- open a few tabs
- open some videos in tabs (e.g. youtube, blib.tv, hyves.nl, facebook)
- watch everything crawling, and even the simplest things like activating a window or typing text are slow.
- the load jumps up to ~6.

After closing tabs, or closing Konqueror, nspluingviewer will continue to consume system resources (or bogging the X server). Even exiting konqueror won't stop nspluginviewer.

Temporary disabling compositing effects have no effect either.

After killing nspluginviewer, things get back to normal, and the load gets back to ~0.30

My specs:
- Intel MacBook 1.83 GHz
- 512 MB DDR2 SDRAM
- Intel integrated graphics chipset 945GM
- openSUSE 11.1
- X.org 7.4 with compositing / kwin effects.
- flash player 10.0.22.87

Comment 1 Diederik van der Boor 2009-07-01 00:11:31 UTC

Additional notes:
- plugin priority is set to "low" in Konqueror.
- firefox plays the movies just fine. Still have some slowdown, but the system doesn't freeze like it happens with Konqueror.

Comment 2 FiNeX 2009-07-01 10:44:53 UTC

I can confirm this behaviour: I use "killall nspluginviewer" frequently.

KDE trunk 
Qt 4.5.1
Flash plugin 10.0.22.87
Xorg 1.6.1
Nvidia driver 185.18.14

Comment 3 FiNeX 2009-07-01 10:47:06 UTC


*** This bug has been marked as a duplicate of bug 182869 ***