SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 2013-01-18 03:05:25

shengchieh
#! Die Hard
Registered: 2009-01-07
Posts: 585

#! is slow; is process running? WORKAROUNDED, BUT WHY?

#! 11 seems to be significantly slower than #! 10 (I just installed yesterday).  Is a process running that shouldn't be?  Below is
my process list.

shengchieh@crunchbang:~$ ps -ef
UID           PID  PPID  C STIME TTY          TIME CMD
root            1     0  0 15:10 ?        00:00:01 init [2]  
root            2     0  0 15:10 ?        00:00:00 [kthreadd]
root            3     2  0 15:10 ?        00:00:00 [ksoftirqd/0]
root            6     2  0 15:10 ?        00:00:00 [migration/0]
root            7     2  0 15:10 ?        00:00:00 [watchdog/0]
root            8     2  0 15:10 ?        00:00:00 [cpuset]
root            9     2  0 15:10 ?        00:00:00 [khelper]
root           10     2  0 15:10 ?        00:00:00 [kdevtmpfs]
root           11     2  0 15:10 ?        00:00:00 [netns]
root           12     2  0 15:10 ?        00:00:00 [sync_supers]
root           13     2  0 15:10 ?        00:00:00 [bdi-default]
root           14     2  0 15:10 ?        00:00:00 [kintegrityd]
root           15     2  0 15:10 ?        00:00:00 [kblockd]
root           17     2  0 15:10 ?        00:00:00 [khungtaskd]
root           18     2  0 15:10 ?        00:00:17 [kswapd0]
root           19     2  0 15:10 ?        00:00:00 [ksmd]
root           20     2  0 15:10 ?        00:00:00 [fsnotify_mark]
root           21     2  0 15:10 ?        00:00:00 [crypto]
root          100     2  0 15:10 ?        00:00:00 [khubd]
root          119     2  0 15:10 ?        00:00:00 [ata_sff]
root          123     2  0 15:10 ?        00:00:00 [scsi_eh_0]
root          124     2  0 15:10 ?        00:00:00 [scsi_eh_1]
root          177     2  0 15:10 ?        00:00:00 [jbd2/sda1-8]
root          178     2  0 15:10 ?        00:00:00 [ext4-dio-unwrit]
root          307     1  0 15:10 ?        00:00:00 udevd --daemon
root          418     2  0 15:10 ?        00:00:00 [kpsmoused]
root          445     2  0 15:10 ?        00:00:00 [cfg80211]
root         1570     1  0 15:10 ?        00:00:00 /usr/sbin/rsyslogd -c5
root         1592     1  0 15:10 ?        00:00:00 /usr/bin/slim -d
root         1602  1592  4 15:10 tty7     00:10:08 /usr/bin/X11/X -nolisten tcp -auth /var/run/slim.auth vt07
root         1633     1  0 15:10 ?        00:00:00 /usr/sbin/cron
101          1650     1  0 15:10 ?        00:00:01 /usr/bin/dbus-daemon --system
avahi        1663     1  0 15:10 ?        00:00:00 avahi-daemon: running [crunchbang.local]
avahi        1664  1663  0 15:10 ?        00:00:00 avahi-daemon: chroot    helper
root         1677     1  0 15:10 ?        00:00:00 /usr/sbin/bluetoothd
root         1685     2  0 15:10 ?        00:00:00 [krfcommd]
root         1707   307  0 15:10 ?        00:00:00 udevd --daemon
root         1710     1  0 15:10 ?        00:00:00 /usr/sbin/cupsd -C /etc/cups/cupsd.conf
colord       1712     1  0 15:10 ?        00:00:00 /usr/lib/i386-linux-gnu/colord/colord
colord       1716     1  0 15:10 ?        00:00:01 /usr/lib/i386-linux-gnu/colord/colord-sane
root         1800     1  0 15:10 ?        00:00:01 /usr/sbin/NetworkManager
root         1809     1  0 15:10 ?        00:00:00 /usr/lib/policykit-1/polkitd --no-debug
root         1821     1  0 15:10 ?        00:00:00 /usr/sbin/modem-manager
ntp          1823     1  0 15:10 ?        00:00:02 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 104:109
root         1837     1  0 15:10 ?        00:00:02 /sbin/wpa_supplicant -u -s -O /var/run/wpa_supplicant
root         1860  1800  0 15:10 ?        00:00:00 /sbin/dhclient -d -4 -sf /usr/lib/NetworkManager/nm-dhcp-client.
root         1878     1  0 15:11 ?        00:00:00 /usr/sbin/minissdpd -i 0.0.0.0
root         1886     1  0 15:11 tty1     00:00:00 /sbin/getty 38400 tty1
root         1887     1  0 15:11 tty2     00:00:00 /sbin/getty 38400 tty2
root         1888     1  0 15:11 tty3     00:00:00 /sbin/getty 38400 tty3
root         1889     1  0 15:11 tty4     00:00:00 /sbin/getty 38400 tty4
root         1890     1  0 15:11 tty5     00:00:00 /sbin/getty 38400 tty5
root         1891     1  0 15:11 tty6     00:00:00 /sbin/getty 38400 tty6
shengchieh   1938     1  0 15:11 ?        00:00:00 /usr/bin/gnome-keyring-daemon --daemonize --login
root         1941     1  0 15:11 ?        00:00:00 /usr/sbin/console-kit-daemon --no-daemon
shengchieh   2014  1592  0 15:11 ?        00:00:04 /usr/bin/openbox --startup /usr/lib/openbox/openbox-autostart OP
shengchieh   2058  2014  0 15:11 ?        00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session x-se
shengchieh   2061     1  0 15:11 ?        00:00:00 /usr/bin/dbus-launch --exit-with-session x-session-manager
shengchieh   2062     1  0 15:11 ?        00:00:00 /usr/bin/dbus-daemon --fork --print-pid 6 --print-address 8 --se
shengchieh   2072     1  0 15:11 ?        00:00:01 tint2
shengchieh   2073     1  0 15:11 ?        00:00:00 pnmixer
shengchieh   2076     1  0 15:11 ?        00:00:00 thunar --daemon
shengchieh   2081     1  0 15:11 ?        00:00:01 xscreensaver -no-splash
shengchieh   2082     1  0 15:11 ?        00:01:12 clipit
shengchieh   2093     1  0 15:11 ?        00:00:00 xfce4-volumed
shengchieh   2094     1  0 15:11 ?        00:00:00 xfce4-power-manager
shengchieh   2099     1  0 15:11 ?        00:00:00 /usr/lib/gvfs/gvfsd
shengchieh   2101     1  0 15:11 ?        00:00:00 /usr/lib/xfce4/xfconf/xfconfd
shengchieh   2102     1  0 15:11 ?        00:00:00 /usr/bin/python /usr/bin/system-config-printer-applet
shengchieh   2103     1  0 15:11 ?        00:00:01 nm-applet
shengchieh   2108     1  0 15:11 ?        00:00:00 /usr/lib/gvfs//gvfs-fuse-daemon -f /home/shengchieh/.gvfs
root         2110     1  0 15:11 ?        00:00:00 /usr/lib/upower/upowerd
shengchieh   2121     1  0 15:11 ?        00:00:00 /usr/bin/pulseaudio --start --log-target=syslog
rtkit        2123     1  0 15:11 ?        00:00:00 /usr/lib/rtkit/rtkit-daemon
shengchieh   2166     1  0 15:11 ?        00:00:00 /usr/lib/i386-linux-gnu/gconf/gconfd-2
shengchieh   2174     1  0 15:11 ?        00:00:42 compton --vsync opengl
shengchieh   2285     1  0 15:11 ?        00:01:20 conky -q
root         2351   307  0 15:32 ?        00:00:00 udevd --daemon
root         2412     2  0 17:48 ?        00:00:00 [flush-8:0]
root         2437     2  0 18:05 ?        00:00:02 [kworker/0:2]
root         2453     2  0 18:11 ?        00:00:02 [kworker/0:0]
shengchieh   2674     1  0 18:16 ?        00:00:00 /usr/lib/gvfs/gvfs-gdu-volume-monitor
root         2677     1  0 18:16 ?        00:00:00 /usr/lib/udisks/udisks-daemon
root         2678  2677  0 18:16 ?        00:00:00 udisks-daemon: polling /dev/sr0
shengchieh   2681     1  0 18:16 ?        00:00:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
shengchieh   2683     1  0 18:16 ?        00:00:00 /usr/lib/gvfs/gvfs-afc-volume-monitor
shengchieh   3118  2014  0 18:26 ?        00:00:03 /usr/bin/python /usr/bin/obmenu
shengchieh   3119  2014  0 18:27 ?        00:00:02 /usr/bin/python /usr/bin/terminator
shengchieh   3122  3119  0 18:27 ?        00:00:00 gnome-pty-helper
shengchieh   3123  3119  0 18:27 pts/0    00:00:00 /bin/bash
root         3311     2  0 18:40 ?        00:00:00 [kworker/0:3]
root         3312     2  0 18:40 ?        00:00:00 [kworker/u:1]
root         3425     2  0 18:50 ?        00:00:00 [kworker/u:2]
shengchieh   3427  2014 15 18:53 ?        00:00:24 iceweasel
shengchieh   3457  3123  0 18:56 pts/0    00:00:00 ps -ef

Is there any runaway process or is there something else slowing things down?
It's annoying to wait forever.

Sheng-Chieh

Last edited by shengchieh (2013-01-18 23:16:12)

Offline

Help fund CrunchBang, donate to the project!

#2 2013-01-18 04:17:48

moetunes
#! Member
Registered: 2012-10-06
Posts: 75

Re: #! is slow; is process running? WORKAROUNDED, BUT WHY?

The easiest way to check is to open a terminal and run the program top and check the cpu column.
If you don't have much memory and the system keeps using swap could be another reason.

Offline

#3 2013-01-18 05:05:36

shengchieh
#! Die Hard
Registered: 2009-01-07
Posts: 585

Re: #! is slow; is process running? WORKAROUNDED, BUT WHY?

Thank you for replying.

I took two snapshot of top

  PID USER         PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND                                           
 1602 root         20   0 86440 6252 1440 R  16.0  2.5  13:56.53 Xorg                                              
 3427 shengchieh   20   0  398m  67m  14m S  14.2 28.0   3:01.50 iceweasel                                         
 3119 shengchieh   20   0 68644 7096 3384 S   2.9  2.9   0:07.01 /usr/bin/termin                                   
 2174 shengchieh   20   0 25300  440  276 S   1.6  0.2   0:55.84 compton                                           
 2285 shengchieh   20   0 51148  760  452 S   0.8  0.3   1:52.51 conky                                             
 2014 shengchieh   20   0 14816 2876 1252 S   0.3  1.2   0:05.39 openbox                                           
 2082 shengchieh   20   0 26812 1372  944 S   0.3  0.6   1:36.23 clipit                                            
 3582 root         20   0     0    0    0 S   0.3  0.0   0:01.02 kworker/0:1                                       
    1 root         20   0  2280    0    0 S   0.0  0.0   0:01.32 init                                              


  PID USER         PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND                                           
 1602 root         20   0 87064 6796 2036 S  21.4  2.8  14:09.17 Xorg                                              
 3427 shengchieh   20   0  398m  41m 7472 S  15.5 17.4   3:11.13 iceweasel                                         
 3119 shengchieh   20   0 68644 9.9m 4556 S   5.6  4.1   0:08.09 /usr/bin/termin                                   
 2174 shengchieh   20   0 25300  864  380 S   1.3  0.4   0:56.88 compton                                           
 2285 shengchieh   20   0 51148  756  452 S   0.7  0.3   1:52.92 conky                                             
 3603 shengchieh   20   0  4604 1356  996 R   0.7  0.6   0:00.42 top                                               
 2082 shengchieh   20   0 26812 1476  996 S   0.3  0.6   1:36.50 clipit                                            
 2683 shengchieh   20   0 19096    0    0 S   0.3  0.0   0:00.74 gvfs-afc-volume                                   
 3604 shengchieh   20   0 44312  15m  10m S   0.3  6.6   0:02.41 geany                                             
    1 root         20   0  2280    0    0 S   0.0  0.0   0:01.32 init                                              
    2 root         20   0     0    0    0 S   0.0  0.0   0:00.00 kthreadd                                          
    3 root         20   0     0    0    0 S   0.0  0.0   0:00.94 ksoftirqd/0      

Do you people see anything fishy?

I only have 256 MB memory.  When I install I thought #! defaulted to 492 MB (or something close to it) memory.
It is the same desktop I used for #! 10 which was much faster.  #! 11 semms sluggish.

Btw, this is the second time I'm writing this.  #! 11 just crashed on me
while writing the 1st time.  That was the 2nd crash in 2 days - not a
good sign.  I'm thinking of reversing back to #! 10 or try something else.

Sheng-Chieh

Offline

#4 2013-01-18 07:31:28

moetunes
#! Member
Registered: 2012-10-06
Posts: 75

Re: #! is slow; is process running? WORKAROUNDED, BUT WHY?

With only 256mB memory and using iceweasel there will be a fair amount of swapping going on. Do you have much swap available? What does   free -m   in a terminal return?

Offline

#5 2013-01-18 11:47:37

MidGe
Member
Registered: 2012-05-27
Posts: 29

Re: #! is slow; is process running? WORKAROUNDED, BUT WHY?

Hi there,

It may be sheer coincidence but I experience a similar problem since about 5 hours ago. Even typing this is slow. There is a lag between the time I type and the letters appearing on the screen (only in Ice Weasel).

In my case it definitely is not a memory issue or a CPU issue.  Idle show 100% or close (12 cores) and my memory (16Gb) use is around 10%.

I really wish I could easily get rid of IceWeasel and install Firefox.  And, no, they are not the same thing...  Close but not the same!

Offline

#6 2013-01-18 17:50:43

shengchieh
#! Die Hard
Registered: 2009-01-07
Posts: 585

Re: #! is slow; is process running? WORKAROUNDED, BUT WHY?

moetunes,

$ free -m
             total       used       free     shared    buffers     cached
Mem:           240        236          3          0          6        131
-/+ buffers/cache:         99        141
Swap:          492         75        417

I'm going try #! 11 non-PAE version 32 bits - I have #! 11 PAE 32 bits.  There shouldn't be a reason why PAE won't work,
but it worth a shot.

Sheng-Chieh

Offline

#7 2013-01-18 20:06:05

moetunes
#! Member
Registered: 2012-10-06
Posts: 75

Re: #! is slow; is process running? WORKAROUNDED, BUT WHY?

It doesn't seem to be using alot of swap so that's probably not it. Starting with a fresh browser profile might be worth a try. Nothing else comes to mind atm...

Offline

#8 2013-01-18 23:15:13

shengchieh
#! Die Hard
Registered: 2009-01-07
Posts: 585

Re: #! is slow; is process running? WORKAROUNDED, BUT WHY?

Clearing the browser configuration will not help.  Everything was slow, e.g., terminal, install printer, etc.

I installed non-PAE version of #! 11 (wasn't much work since I hardly did anything w/ #! 11 PAE).  Speed seems fine.
I'm surprised that PAE version didn't work for this desktop.  I know the desktop is a dinosaur, but it is still a Pentium.

While this thread is resolved, I'm curious to understand what happened.  My desktop hardware specs are

http://shengchieh.50webs.com/Desktoplshw.txt
http://shengchieh.50webs.com/Desktoplspci.txt    (#! 10)

Can anyone explains why non-PAE #! 11 works fine, but not PAE #! 11.

Sheng-Chieh

Offline

#9 2013-01-19 05:50:56

MidGe
Member
Registered: 2012-05-27
Posts: 29

Re: #! is slow; is process running? WORKAROUNDED, BUT WHY?

Having done a bit more digging, the issue seems to be JSON related.

An immediate workaround was to exit iceweasel, delete two JSON related files from the .mozilla profile folder, and re-start iceweasel.  And, presto, iceweasel is back to speed without any ill-effects for the time being it seems.

The two files I deleted were: ".parentlock" and "webapps.json".

Do at your own risk as I am not ceratin about all implications of this move, but it sure beats a re-install of iceweasel, if not the whole OS.  smile

Offline

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.

Debian Logo