Results 1 to 10 of 10

Thread: How to deal with npviewer.bin

  1. #1
    Join Date
    Jun 2007
    Location
    Toronto
    Beans
    76

    How to deal with npviewer.bin

    From the homework that I've been doing and personal experience, this process goes nutso (takes up 20-50% of CPU usage) on 64-bit Ubuntu when running Flash on Firefox. Up until now, I'd open System Monitor, scroll to it, click on it and click on End Process.
    After reading a thread in the archives, I came across some command line solutions http://ubuntuforums.org/showthread.php?t=647961 I figured, why not make it easy? Just create a launcher with the killall npviewer.bin command and click on it every time you hear the fan goin' crazy.

  2. #2
    Join Date
    Apr 2008
    Location
    Texas
    Beans
    21
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: How to deal with npviewer.bin

    I'm having similar problem and have also done some research. Looks like this problem has been around a while, at least since early 2008.

    I did a "top" and saw npviewer listed as hogging the cpu.

    I like your idea and have implemented it. Thanks.

  3. #3
    Join Date
    Jul 2007
    Location
    UK
    Beans
    17,058
    Distro
    Ubuntu Development Release

    Re: How to deal with npviewer.bin

    If it's the 32bit plugin on 64 bit giving headache then uninstall it and
    try the 64 bit plugin from adobe.

    http://labs.adobe.com/technologies/flashplayer10/

  4. #4
    Join Date
    Jun 2007
    Location
    Toronto
    Beans
    76

    Re: How to deal with npviewer.bin

    AFIK it's not running under the wrapper. I'd figure that the stock FF install would automatically install the apropriate driver, unless I'm WAY off and there are some issues with the 64bit driver that I'm not aware of. I try to keep my system and packages relatively stock unless there are serious functionality issues (don't get me started on suspend) or I'm helping a developer test something.
    This method at least turns a major annoyance into a minor one.

  5. #5
    Join Date
    Jun 2007
    Location
    Toronto
    Beans
    76

    Re: How to deal with npviewer.bin

    If you're also running Opera, this command in the launcher will take care of both browsers in 1 shot:
    killall -9 npviewer.bin /usr/lib/opera/operapluginwrapper-ia32-linux /usr/lib/flashplugin-installer/libflashplayer.so
    I click on it every time I hear the fan come on

  6. #6
    Join Date
    Jul 2007
    Beans
    128
    Distro
    Xubuntu 12.04 Precise Pangolin

    Lightbulb Re: How to deal with npviewer.bin

    I can totally vouch on the npviewer issues as I have been experiencing them for quite a while. Here's the story as I understand it:

    Adobe makes a 32-bit and 64bit version of flash for linux/mozilla. Their 32-bit version is more or less considered stable and their 64-bit versions have been in alpha most of the time. At the time of this reply, 64-bit ubuntu's flashplayer-nonfree package installs the 32-bit version and then uses npviewer (or nsplugin) to adapt it to work in 64bit land.

    In my view this adapter is a real pain in the bottom. It may end up hogging memory, using up CPU, freezing up the browser, crashing flash altogether and resulting in blank boxes until the browser is restarted, hanged processes, the whole nine yards.

    So why do we even waste our time adapting the 32-bit version to work in 64-bit?

    My best guess is that it is hit-and-miss with the 64-bit version of the plugin: either it works well or not at all. It is possible to remove the ubuntu-installed flash, do a search for "flash plugin, ubuntu 64-bit alpha" and some relevant links come up, particularly, look for a 64-bit download from the adobe site. I have successfully used the alpha version before. After upgrading to 9.10, nsplugin was back. Removing the 32-bit flash and installing the 64-bit flash resulted in unusable problems-this doesn't mean it won't work for you though.

    I pray for the hypothetical day when Gnash manages to trivialize the Adobe problem.

  7. #7
    Join Date
    Nov 2006
    Beans
    14

    Re: How to deal with npviewer.bin

    FWIW, the 64 bit plugin is here:

    http://labs.adobe.com/downloads/flas...r10_64bit.html

    Haven't tried it yet so can't speak to its quality. But npviewer.bin is killn' me.

  8. #8
    Join Date
    Mar 2006
    Location
    Greece-Hellas
    Beans
    5
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: How to deal with npviewer.bin

    Or, if you run Compiz, you can assign a key combination to execute the command "killall npviewer.bin". My combination is Alt+z so it becomes handy when the cpu usage getting high.

    System -> Preferences -> CompizConfig... -> in "General" group you choose "Commands". Then it's easy to deal with it.

    Hope it helps...

  9. #9
    Join Date
    Feb 2006
    Beans
    205

    Re: How to deal with npviewer.bin

    Quote Originally Posted by jsilve1 View Post
    FWIW, the 64 bit plugin is here:

    http://labs.adobe.com/downloads/flas...r10_64bit.html

    Haven't tried it yet so can't speak to its quality. But npviewer.bin is killn' me.

    Tried the 64bit version. npviewer is gone, but instead, Firefox take about 40% of CPU nearly constantly with 30 tabs open. Then I installed flashblock extension, it is now down to about 5%.

  10. #10
    Join Date
    Aug 2006
    Beans
    13

    Re: How to deal with npviewer.bin

    Quote Originally Posted by FiReSTaRT View Post
    From the homework that I've been doing and personal experience, this process goes nutso (takes up 20-50% of CPU usage) on 64-bit Ubuntu when running Flash on Firefox. Up until now, I'd open System Monitor, scroll to it, click on it and click on End Process.
    After reading a thread in the archives, I came across some command line solutions http://ubuntuforums.org/showthread.php?t=647961 I figured, why not make it easy? Just create a launcher with the killall npviewer.bin command and click on it every time you hear the fan goin' crazy.
    Do you have an icon for this????

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •