roughly 90% of the time i use the file browser it seems to go into a loop of maximum processor usage. This appears to happen on directorys with a large number of items but that may be unrelated since most of my directorys have a large number of items :)
Description
Event Timeline
Logged In: YES
user_id=103
And then what's the bug? You can investigate this with much more precision and information.
- is it drawing causing it?
- only when it tries to read, redraw is fast?
- network drives? local drives?
- isn't 99% processor loops in blender normal in other cases?
- can you redo this on other computers?
- is this in older blender versions too?
Logged In: YES
user_id=2923
"And then what's the bug? "
Sorry - I mean the 99% processor usage continues for roughly 5 minutes for no apparent reason. I eventually am able to select a file and then eventually able to press the open button).
You can investigate this with much more precision and information.
- is it drawing causing it?
Possibly but I don't think so - I do have slow highlighting of text ie if I drag over a file there is a lag before it highlights. Also scrolling is always jerky even when I don't hit the semi-permanent processor spiking. Also it does cause the processor to work quite a bit harder (ie my fan turns on).
- only when it tries to read, redraw is fast?
redraw is never fast, but it seems to be when I go to select a file that the problem occurs.
- network drives? local drives?
local drive haven't tried a network drive, don't have a network locally to test, but will try at school
- isn't 99% processor loops in blender normal in other cases?
for a few seconds or during heavy work like rendering yes. For minutes on end for no apparent reason - no.
- can you redo this on other computers?
will try on the school computers
- is this in older blender versions too?
yes, I think every blender version I've used - just realized that my 95% appears to be wrong since browsing for a file from a fresh loaded blender I'm having difficult triggering it. I guess my file browsing is almost always after working on something for a while and then going to save. Although I do seem to recall some occurances on trying to open files from a freshly opened Blender.
Also the text that shows the path selected and the file selected is using different display code than the text used by area displaying the list of files in the directory since there is no slower interaction with the text in the path, but there is in text in the directory list.
Logged In: YES
user_id=103
Ok, so it's redrawing i guess... moving cursor in filewindow invokes redraws, to show the active file.
You might suffer this not-so-rare video card that hates glbitmap.
Logged In: YES
user_id=3002
yes, this sounds like one my evil old ATI card. the best
thing to do is to enable ICONV in the build system; this
will allow using international fonts in the file window,
which are textured and should go a LOT faster.
Or, if you don't want to do that, search filesel.c and
replace all "glRasterPos2i" next to a "BMF_DrawString" with
"BIF_RasterPos" and "BIF_DrawString" (this function will
require adding 0 as a third argument). Make sure to include
"BIF_language.h" in filesel.c too.
Joe
Logged In: YES
user_id=103
I still cannot believe why ATI wouldn't support bitmap drawing. It's such a basic simple old opengl function... best is to carefully check on driver upgrades/downgrades or options for drivers.
(Moved to opengl section)
This is a generic request to test your bug report and see if it is still an issue in 2.5alpha2 if so please let me know by making a comment in this report ie 'also in 2.5alpha2' and I will add it to the 2.5 bug list.