Announcement

Collapse
No announcement yet.

Jockey just sitting there, hogging memory

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Jockey just sitting there, hogging memory

    Last week, as an experiment, I wanted to try a build-from-scratch Kubuntu. As usual, my HP Mini 2140 served as my lab bench. (Sorry, oshunluvr, I just can't get into E17; Bodhi, while admirable, had to go...)

    First I installed the netboot mini. Next I installed kde-standard, kde-plasma-desktop, and kde-plasma-netbook. Next it became time to get the Mini's deplorable BCM4322 wireless to work. Because I've grown supremely annoyed at that thing, I installed Jockey to let it do the work. (HP has actually configured the BIOS to refuse to boot if it detects something other than a Broadcom wireless card!)

    I continued my experiment, installing additional packages. All was going very well. Just out of curiosity, I pressed [Ctrl]+[Esc] to see what was in memory -- and there sat two Jockey processes, consuming about 50 MB of RAM. "I'm done with that thing," I thought, "so why is it running, even after a reboot?"

    I uninstalled both jockey-common and jockey-kde; my wireless continues to work. Now I'm wondering if anyone else who's used Jockey for anything notices the same thing -- is it lurking in your RAM?
    Tags: None
    • Top
    • Bottom
    #2
    Re: Jockey just sitting there, hogging memory

    I used it to install the nvidia driver during initial setup (11.04) and it's not running now. Out of curiosity, I launched it and let it search in vain for new drivers. After closing it down, jockey-backend remains active and uses 28 MB but does not survive a reboot.

    Also notable is although I launched it as user the backend is owned by root. Effectively making it impossible for a regular user to end the process.

    Possibly you've uncovered a bug or bad programming. I suppose it's searching for new hardware? Probably worth a query to the dev.

    Oh - and NP on the Bodhi, I'm not paid for my endorsements anyway!

    Please Read Me
    • Top
    • Bottom

    Comment

      #3
      Re: Jockey just sitting there, hogging memory

      Update: I left jockey-backend running and the activity window open just to see if it dies on it's own. It does after about 10 minutes.

      I wonder if yours behaves the same.

      Please Read Me
      • Top
      • Bottom

      Comment

      Previous template Next
      Working...
      X