Bug 309682 - Browsing to a directory with lots of .gz files causes the dialog to become unresponsive...
Summary: Browsing to a directory with lots of .gz files causes the dialog to become un...
Status: RESOLVED DUPLICATE of bug 293888
Alias: None
Product: kfile
Classification: Applications
Component: general (show other bugs)
Version: 4.9.1
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-07 08:32 UTC by Adam Jorgensen
Modified: 2013-07-21 14:40 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Jorgensen 2012-11-07 08:32:48 UTC
If, while using an Open File Dialog, I try to open a directory that contains lots (I.e. Hundreds of .gz files) the dialog becomes completely unresponsive for a very long time.

Attempting to close the dialog results in the Terminate Process window being displayed but attempting to terminate the KDialog process is also unresponsive.

Repeated attempts to close and kill the KDialog process result in KWin becoming completely unresponsive (I.e. Unable to switch desktops, change windows, activate menus, etc)

Reproducible: Always

Steps to Reproduce:
1. Create a directory and fill it with hundreds of .gz files
2. Start and Chromium
3. Hit CTRL+O to Open a File
4. Navigate to the directory filled with .gz files
5. Observe Dialog window become unresponsive until it has inspected every file
Actual Results:  
Dialog windows becomes unresponsive, even to kill requests

Expected Results:  
Dialog window should still respond and make it possible to abort loading the directory, return to the previous directory or close the dialog box.
Comment 1 Jekyll Wu 2013-03-12 04:19:56 UTC
Can't reproduce using kDE SC 4.10.1 .

I also use Gentoo, so it is common that the distfiles folder contains hundreds of source code tarballs.  Navigating to that folder in the dialog just works fine for me.
Comment 2 Christoph Feck 2013-07-21 14:40:48 UTC
Note that the reporter uses Chrome, not a KDE application, which invokes the file dialog indirectly via kdialog. See bug 293888 comment #15.

*** This bug has been marked as a duplicate of bug 293888 ***