Opened 19 years ago
Closed 17 years ago
#355 closed bug (fixed)
[Tracker] slow content loading
Reported by: | diver | Owned by: | axeld |
---|---|---|---|
Priority: | critical | Milestone: | R1/alpha1 |
Component: | Applications/Tracker | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
Tracker is slow when loading files in icon view or mini icon view. To reproduce open haiku volume from desktop and press alt+2 to switch to miniicon mode and close this window. Open it again and go to /boot/beos/bin. It will take 20 seconds to show content.
Tested with freshly downloaded rev16908 under vmware.
Change History (10)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
bug_group: | → developers |
---|
comment:3 by , 18 years ago
Description: | modified (diff) |
---|---|
Platform: | → All |
Priority: | normal → critical |
comment:4 by , 17 years ago
Milestone: | R1 → R1/alpha |
---|
comment:7 by , 17 years ago
I just rechecked it in hrev23287 following the method listed above and it still goes slow as was first reported. This was on real hardware, my test laptop a Thinkpad 570E.
comment:8 by , 17 years ago
Indeed, i could reproduce it consistently on real hardware and vmware, but only with a fresh image/install.
Apparently, if you already (even after a reboot) visited a directory in mini icon mode before doing the above steps, then the bug doesn't show.
Example steps: a- Start with a _fresh_ haiku image or install b- Go to boot/beos/bin c- Switch to mini icon view (no bug here) d- Close the window
From there, you can't reproduce the orignal ticket's bug. The bug appears with boot/beos/system boot/beos/apps etc.. until you visited them one time, even after a reboot.
Can you confirm this?
hope this helps, alex
comment:9 by , 17 years ago
Status: | new → assigned |
---|
Definitely! I investigated the problem a bit, and it occurs because Tracker cannot read the "pose info" attribute from the files and retries 10 times for each time - with a timeout of 10 ms between each try. I have no idea why this doesn't happen on BeOS yet (don't have a BeOS machine here right now :-().
comment:10 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
ixed in hrev23376. What were they thinking??? :-)
This manipulation also deadlock appserver. It happens to me already several times.