VectorLinux
October 20, 2014, 04:17:29 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to http://vectorlinux.com/forum1. The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
 
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: [1]
  Print  
Author Topic: What makes Thunar so painfully slow to open the first directory?  (Read 5097 times)
rhauff
Vectorite
***
Posts: 105


« on: May 23, 2007, 07:40:20 am »

I'm running 5.8 Std on 2 machines, an 800 and a 2000 Mhz.  Thunar itself opens quickly and displays the default home directory and contents, but when I click on a directory to view it, it locks up the CPU for 20-30 seconds 'til it displays the contents.  After that other directories display quickly.

I have tried shutting off thumbnails and other option, but it is still as slow.  XFE by comparison displays the directories instantly.
Logged
lagagnon
Global Moderator
Vectorian
*****
Posts: 1922



WWW
« Reply #1 on: May 23, 2007, 09:10:46 am »

I don't know the answer to that but you might try the xfce forums for more information:

http://forum.xfce.org/
Logged

"As people become more intelligent they care less for preachers and more for teachers". Robert G. Ingersoll
rhauff
Vectorite
***
Posts: 105


« Reply #2 on: May 23, 2007, 10:13:31 am »

Good tip.  I just looked there, and can't find anything similar.

I just found it's the "Tree" view, View-Side Pane-Tree, that causes the problem.  Shortcut view is fast.
Tree view apparently loads the directory contents of all subdirectories to enable the active tree.  If I go out of Home, up to File System, then I have the Looooong delay as it reads all the dirs and subdirs from root level.

So, I don't know if there is a solution, but Shortcut view works well, just not as convenient.

Roland
Logged
Pita
Vectorian
****
Posts: 1311


« Reply #3 on: May 24, 2007, 08:04:47 pm »

VL-5.8-Gold
Just tried thunar and I have no such problem. Files pop-up almost instantly regardless of view set. I never use thunar so.
Sorry not much help.
Logged
tomh38
Vectorian
****
Posts: 913



« Reply #4 on: May 25, 2007, 01:08:14 am »

I've been using Thunar since 5.8 came out, and I've never seen this problem.  Sorry I can't be of help.


AMD Athlon 1.1 Ghz, 512 RAM, nVidia 128 RAM (until my new mobo arrives later today Grin).
« Last Edit: May 25, 2007, 01:11:33 am by tomh38 » Logged

"I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones." - Linus Torvalds, April 1991
GrannyGeek
Packager
Vectorian
****
Posts: 2567


« Reply #5 on: May 25, 2007, 09:04:56 am »

I have also not seen this problem with Thunar. I've checked on two of my three 5.8 Standard Gold systems. The other system is not turned on.
--GrannyGeek
Logged

Registered Linux User #397786

Happily running VL 7 Gold on  a Sempron LE-1300 desktop (2.3 GHz), 4 G RAM,  GeForce 6150 SE onboard graphics and on an HP Pavilion dv7 i7, 6 gigs, Intel 2nd Generation Integrated Graphics Controller
Triarius Fidelis
Vecteloper
Vectorian
****
Posts: 2399


Domine, exaudi vocem meam


WWW
« Reply #6 on: May 25, 2007, 01:46:07 pm »

I wonder if strace would be of any use here.

Maybe it's polling some resource repeatedly??
Logged

"Leatherface, you BITCH! Ho Chi Minh, hah hah hah!"

Formerly known as "Epic Fail Guy" and "Döden" in recent months
rhauff
Vectorite
***
Posts: 105


« Reply #7 on: May 25, 2007, 05:15:39 pm »

I haven't tried strace before, it sure dumps a lot of info!  This looks like it'll take me a while to sift through, but I'll see if I can find anything.
Logged
Triarius Fidelis
Vecteloper
Vectorian
****
Posts: 2399


Domine, exaudi vocem meam


WWW
« Reply #8 on: May 28, 2007, 04:16:08 pm »

Yes it does. See if there is any obsessive calling (thousands of times) of the same system call anywhere. Don't be alarmed by the repeated checks for standard libraries in different places, because these are standard with any dynamically-linked binary on Linux (or other systems for that matter), and take negligible resources.
Logged

"Leatherface, you BITCH! Ho Chi Minh, hah hah hah!"

Formerly known as "Epic Fail Guy" and "Döden" in recent months
rhauff
Vectorite
***
Posts: 105


« Reply #9 on: May 30, 2007, 09:58:55 am »

Here's some very interesting information on this (to someone, I hope!):
If I open Thunar from the panel, click File System on the left (tree view), then /etc, it takes 53 seconds to load.
If I open Thunar from a terminal, it takes 22 seconds for the same process.  Here's the terminal log:

vector:/~
roland:$ thunar
thread 0x8301318 started for pool 0x80f8a98.
thread 0x8301318 in pool 0x80f8a98 waits for up to a 1/2 second for task (1 running, 1 unprocessed).
thread 0x8301318 in pool 0x80f8a98 calling func.
thread 0x83fcdd0 started for pool 0x8102370.
thread 0x83fcdd0 in pool 0x8102370 waits for up to a 1/2 second for task (3 running, 3 unprocessed).
thread 0x83fcdd0 in pool 0x8102370 calling func.
thread 0x83fe180 started for pool 0x8102370.
thread 0x83fe180 in pool 0x8102370 waits for up to a 1/2 second for task (3 running, 2 unprocessed).
thread 0x83fe180 in pool 0x8102370 calling func.
thread 0x83fd4a0 started for pool 0x8102370.
thread 0x83fd4a0 in pool 0x8102370 waits for up to a 1/2 second for task (3 running, 1 unprocessed).
thread 0x83fd4a0 in pool 0x8102370 calling func.
thread 0x83fcdd0 in pool 0x8102370 waits for up to a 1/2 second for task (3 running, 0 unprocessed).
thread 0x83fe180 in pool 0x8102370 waits for up to a 1/2 second for task (3 running, -1 unprocessed).
thread 0x83fd4a0 in pool 0x8102370 waits for up to a 1/2 second for task (3 running, -2 unprocessed).
pool 0x8102370 not active, thread 0x83fcdd0 will go to global pool (running: false, immediate: true, len: 0).
thread 0x83fcdd0 leaving pool 0x8102370 for global pool.
thread 0x83fcdd0 waiting in global pool for 10.000000 seconds.
pool 0x8102370 not active, thread 0x83fe180 will go to global pool (running: false, immediate: true, len: 0).
thread 0x83fe180 leaving pool 0x8102370 for global pool.
thread 0x83fe180 waiting in global pool for 10.000000 seconds.
pool 0x8102370 not active, thread 0x83fd4a0 will go to global pool (running: false, immediate: true, len: 0).
thread 0x83fd4a0 leaving pool 0x8102370 for global pool.
thread 0x83fd4a0 waiting in global pool for 10.000000 seconds.
thread 0x8301318 in pool 0x80f8a98 waits for up to a 1/2 second for task (1 running, 0 unprocessed).
thread 0x8301318 leaving pool 0x80f8a98 for global pool.

**********************Now clicking File System /etc:  **************************************

thread 0x8404320 started for pool 0x80f8a98.
thread 0x8404320 in pool 0x80f8a98 waits for up to a 1/2 second for task (1 running, 1 unprocessed).
thread 0x8404320 in pool 0x80f8a98 calling func.
thread 0x8402410 started for pool 0x8402248.
thread 0x8402410 in pool 0x8402248 waits for up to a 1/2 second for task (3 running, 3 unprocessed).
thread 0x8402410 in pool 0x8402248 calling func.
thread 0x8402410 in pool 0x8402248 waits for up to a 1/2 second for task (3 running, 2 unprocessed).
thread 0x8402410 in pool 0x8402248 calling func.
thread 0x8402410 in pool 0x8402248 waits for up to a 1/2 second for task (3 running, 1 unprocessed).
thread 0x8402410 in pool 0x8402248 calling func.
pool 0x8402248 not active, thread 0x8402410 will go to global pool (running: false, immediate: false, len: 0).
thread 0x8402410 leaving pool 0x8402248 for global pool.
thread 0x8402410 waiting in global pool for 10.000000 seconds.
thread 0x84338c0 started for pool 0x8402248.
pool 0x8402248 not active, thread 0x84338c0 will go to global pool (running: false, immediate: false, len: 0).
thread 0x84338c0 leaving pool 0x8402248 for global pool.
thread 0x84338c0 waiting in global pool for 10.000000 seconds.
thread 0x83fec50 started for pool 0x8402248.
pool 0x8402248 not active, thread 0x83fec50 will go to global pool (running: false, immediate: false, len: 0).
thread 0x83fec50 leaving pool 0x8402248 for global pool.
thread 0x8404320 in pool 0x80f8a98 waits for up to a 1/2 second for task (1 running, 0 unprocessed).
thread 0x83fec50 waiting in global pool for 10.000000 seconds.
thread 0x8404320 leaving pool 0x80f8a98 for global pool.
thread 0x8402410 entering pool 0x80f8a98 from global pool.
thread 0x8402410 in pool 0x80f8a98 waits for up to a 1/2 second for task (2 running, 2 unprocessed).
thread 0x8402410 in pool 0x80f8a98 calling func.
thread 0x83fec50 entering pool 0x80f8a98 from global pool.
thread 0x83fec50 in pool 0x80f8a98 waits for up to a 1/2 second for task (2 running, 1 unprocessed).
thread 0x83fec50 in pool 0x80f8a98 calling func.
thread 0x84338c0 entering pool 0x8431a28 from global pool.
thread 0x84338c0 in pool 0x8431a28 waits for up to a 1/2 second for task (3 running, 3 unprocessed).
thread 0x84338c0 in pool 0x8431a28 calling func.
thread 0x8430d98 started for pool 0x8431a28.
thread 0x8430d98 in pool 0x8431a28 waits for up to a 1/2 second for task (3 running, 2 unprocessed).
thread 0x8430d98 in pool 0x8431a28 calling func.
thread 0x84bc448 started for pool 0x8431a28.
thread 0x84bc448 in pool 0x8431a28 waits for up to a 1/2 second for task (3 running, 1 unprocessed).
thread 0x84bc448 in pool 0x8431a28 calling func.
thread 0x84338c0 in pool 0x8431a28 waits for up to a 1/2 second for task (3 running, 0 unprocessed).
thread 0x8430d98 in pool 0x8431a28 waits for up to a 1/2 second for task (3 running, -1 unprocessed).
thread 0x84bc448 in pool 0x8431a28 waits for up to a 1/2 second for task (3 running, -2 unprocessed).
pool 0x8431a28 not active, thread 0x84338c0 will go to global pool (running: false, immediate: true, len: 0).
thread 0x84338c0 leaving pool 0x8431a28 for global pool.
thread 0x84338c0 waiting in global pool for 10.000000 seconds.
pool 0x8431a28 not active, thread 0x8430d98 will go to global pool (running: false, immediate: true, len: 0).
thread 0x8430d98 leaving pool 0x8431a28 for global pool.
thread 0x8430d98 waiting in global pool for 10.000000 seconds.
pool 0x8431a28 not active, thread 0x84bc448 will go to global pool (running: false, immediate: true, len: 0).
thread 0x84bc448 leaving pool 0x8431a28 for global pool.
thread 0x84bc448 waiting in global pool for 10.000000 seconds.
thread 0x84338c0 entering pool 0x8431a28 from global pool.
thread 0x84338c0 in pool 0x8431a28 waits for up to a 1/2 second for task (3 running, 3 unprocessed).
thread 0x84338c0 in pool 0x8431a28 calling func.
thread 0x84338c0 in pool 0x8431a28 waits for up to a 1/2 second for task (3 running, 2 unprocessed).
thread 0x84338c0 in pool 0x8431a28 calling func.
thread 0x84338c0 in pool 0x8431a28 waits for up to a 1/2 second for task (3 running, 1 unprocessed).
thread 0x84338c0 in pool 0x8431a28 calling func.
pool 0x8431a28 not active, thread 0x84338c0 will go to global pool (running: false, immediate: false, len: 0).
thread 0x84338c0 leaving pool 0x8431a28 for global pool.
thread 0x84338c0 waiting in global pool for 10.000000 seconds.
thread 0x84338c0 entering pool 0x8431a28 from global pool.
pool 0x8431a28 not active, thread 0x84338c0 will go to global pool (running: false, immediate: false, len: 0).
thread 0x84338c0 leaving pool 0x8431a28 for global pool.
thread 0x84338c0 waiting in global pool for 10.000000 seconds.
thread 0x84338c0 entering pool 0x8431a28 from global pool.
pool 0x8431a28 not active, thread 0x84338c0 will go to global pool (running: false, immediate: false, len: 0).
thread 0x84338c0 leaving pool 0x8431a28 for global pool.
thread 0x84338c0 waiting in global pool for 10.000000 seconds.
thread 0x83fec50 in pool 0x80f8a98 waits for up to a 1/2 second for task (2 running, 0 unprocessed).
thread 0x8402410 in pool 0x80f8a98 waits for up to a 1/2 second for task (2 running, -1 unprocessed).
thread 0x83fec50 leaving pool 0x80f8a98 for global pool.
thread 0x8402410 leaving pool 0x80f8a98 for global pool.

Any ideas?HuhHuhHuhHuh??
Logged
rhauff
Vectorite
***
Posts: 105


« Reply #10 on: May 30, 2007, 10:04:05 am »

I also noticed in htop, there are normally a couple Thunar --daemon's running.  When I click on /etc to open it,  I think I see 8 of them!??
Logged
rhauff
Vectorite
***
Posts: 105


« Reply #11 on: May 30, 2007, 10:17:04 am »

Well this is strange, if I open thunar from the terminal with strace, Thunar itself takes a couple seconds longer to load because of the hundreds of strace messages being logged, but there is NO delay when I click on the /etc or other directories!
Logged
Triarius Fidelis
Vecteloper
Vectorian
****
Posts: 2399


Domine, exaudi vocem meam


WWW
« Reply #12 on: May 31, 2007, 07:26:22 pm »

Sorry. No clue...
Logged

"Leatherface, you BITCH! Ho Chi Minh, hah hah hah!"

Formerly known as "Epic Fail Guy" and "Döden" in recent months
exeterdad
Packager
Vectorian
****
Posts: 2046



« Reply #13 on: May 31, 2007, 08:40:09 pm »

I tried Thunar in both views and /etc opens the same in both. (5.8 Standard)

LOL  I didn't even know there was a tree view until now, Thanks!
Logged
Andy Price
Packager
Vectorite
****
Posts: 237


« Reply #14 on: June 02, 2007, 06:41:09 am »

Rhauff, you're not alone in this problem! I'm running 5.8 Gold on a 1.8 GHz P4 and see the same effect. What's strange is that sometimes there's no delay, other times it takes 10 - 20 seconds to display directory contents. I've switched to Shortcuts view as a workaround as you suggested. Something funny going on...
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!