gtk2 file chooser slow
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gtk+2.0 (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
2. What did you attempt to do, or what did you notice was wrong?
I'm attempting to upload a large numbers of files in a browser (I tried both chrome and firefox). I tried uploading 600+ files to Google drive and it hangs on the upload screen for 2-5 minutes before starting the upload. It appears that the bottleneck is getting the list of files from the file chooser to the browser to start processing, not in the actual upload process it self.
3. What was the expected result, or the expected state?
It should exit the upload screen quickly and start the upload
I'm running into this issue on a Precise desktop. It's not exhibiting the behavior on Lucid desktops.
The project that I'm working on requires uploading hundreds of files at once and has worked fine on Lucid. Now that I've switched to Precise I am unable to work or iterate quickly, incurring 5-10 minute penalties after every code change I make. It's a major work stopping issue for me.
DISTRIB_
DISTRIB_
DISTRIB_ID=Ubuntu
DISTRIB_
stracing reveals:
open("/
fcntl(84, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat(84, {st_mode=
mmap(NULL, 4096, PROT_READ|
lseek(84, 0, SEEK_CUR) = 0
write(84, "<?xml version=\"1.0\" encoding=\"UT"..., 8114176) = 8114176
write(84, "cation name=\"Google Chrome\" exec"..., 1234) = 1234
fstatfs(84, {f_type=
lstat("
fsync(84) = 0
--- SIGPROF (Profiling timer expired) @ 0 (0) ---
close(84) = 0
munmap(
rename(
madvise(
chmod("
--- SIGPROF (Profiling timer expired) @ 0 (0) ---
There are thousands of these files (one for every file the user tried to upload...) and it makes her experience very bad. She ended up following some instructions at http://
-A
affects: | ubuntu → gtk+3.0 (Ubuntu) |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1080890/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]