Description of problem: When opening or creating an Audacity file with 10 or 20 tracks, the interface becomes extremely slow. Opening menus, scrolling, or any other UI action takes several seconds to complete. When you first open audacity with no file open, the UI is normal. When looking at "top" during the slowness, I see that a process called "xfs" is taking up the majority of the processor. Version-Release number of selected component (if applicable): 1.2.5 How reproducible: Happens everytime I get more than a few tracks going (more noticable with more tracks. Steps to Reproduce: 1. Open Audacity 2. import or create 10 or 20 tracks 3. Try menus or other ui elements Actual results: UI is noticably slow. Expected results: Should be as fast as it always is.
I doubt I can do anything do about this, but could you put such an audacity project including its data somewhere, where I can retrieve it?
Ok, I tested it, and it is as you say. On the one hand, we have the component with the tracks which is slow. This is a problem with audacity itself. On the other hand, menus open slowly. It seems that, whenever a menu is displayed, the fonts are looked up. This is why the xfs process gets process time. This seems to be an issue with wxGTK, the toolkit for producing the GUI for audacity. You may try the following: Replace the line FontPath "unix/:7100" in your /etc/X11/xorg.conf with FontPath "/usr/share/X11/fonts/misc" FontPath "/usr/share/X11/fonts/cyrillic" FontPath "/usr/share/X11/fonts/100dpi/:unscaled" FontPath "/usr/share/X11/fonts/75dpi/:unscaled" FontPath "/usr/share/X11/fonts/Type1" FontPath "/usr/share/X11/fonts/100dpi" FontPath "/usr/share/X11/fonts/75dpi" then stop the xfs font server and restart X.
I did not have the line FontPath "unix/:7100" in my xorg.conf (there were no FontPath entries). I did try adding the lines you suggested, but it had no effect. Should this bug be filed upstream with Audacity, or does it show up in other apps that uses wxGTK 1.x widgets?
> Should this bug > be filed upstream with Audacity, or does it show up in other apps that uses > wxGTK 1.x widgets? Yes, please do file a bug upstream.