After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 425368 - Using location bar in directory with many file is very slow
Using location bar in directory with many file is very slow
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
2.10.x
Other All
: Normal major
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
filechooser-retest-and-triage
Depends on:
Blocks:
 
 
Reported: 2007-04-02 05:37 UTC by Michael Partridge
Modified: 2018-04-15 00:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
A very simple and naive program to launch a file chooser in a directory with lots of files (929 bytes, text/plain)
2007-04-02 05:40 UTC, Michael Partridge
Details

Description Michael Partridge 2007-04-02 05:37:40 UTC
If you use the file chooser from >=2.8 in a directory with a large number of files (e.g. more than 1500) and open the location bar then the chooser become unresponsive for a long period.

I've done a bit of profiling using sunstudio (on solaris) and it seem to spend a lot of time in the splay() operations (about 40%) while it's building up the completion list for the chooser entry. In my experiments using a directory with 4000 files it took 50cpu seconds to create the dialog and populate the chooser entry completion list (once populated the completion list operated quite well). Almost all of the time was used in the gtkfilechooserentry.c::files_added_cb() and subfunctions.

I've used gtk+-2.10.6 and gtk+2.10.11 and had the same (or similar) behaviour.
Comment 1 Michael Partridge 2007-04-02 05:40:52 UTC
Created attachment 85683 [details]
A very simple and naive program to launch a file chooser in a directory with lots of files

This was my testcase program. I know it's very simple, but it was enough for me to gather the data.

If you want some profiling results from sunstudio then let me know and I'll see what I can do.
Comment 2 Paolo Borelli 2007-09-15 19:13:04 UTC
Does the patch attached to bug 368931 improve things?
Comment 3 Matthias Clasen 2018-02-10 05:19:34 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 4 Michael Partridge 2018-02-12 02:18:28 UTC
I no longer use GTK and don't have a convenient environment to test. I don't care about this issue, so happy for it to be closed.
Comment 5 Matthias Clasen 2018-04-15 00:19:31 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new