https://bugs.kde.org/show_bug.cgi?id=412894
--- Comment #7 from Bob <jenne...@gmail.com> --- OK, I can understand that. Could it be a little more defensive? Maybe: Check the size of the target and if too big ask for a folder? Or just come back with a “too big” dialog? There may actually be a bug there, too. Please consider the following: 1. When I let it run for 3 days, it apparently corrupted the OS. Safari and Apple App Store started crashing with “invalid instruction codes. 2. On my system, it seems to generate multiple identities for mounted disks remembered from previous instances. Most of the phantom disks show “fail to connect” dialog. The phantoms don’t seem to agree exactly with information I see in finder or disk utility. Could there be a file system interface issue that’s making it worse? On Tue, Dec 31, 2019 at 3:19 PM Maik Qualmann <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=412894 > > --- Comment #6 from Maik Qualmann <metzping...@gmail.com> --- > The Import tool was designed to display images from cameras or memory > cards. So > for a few thousand images. But not for hard drives with tens of thousands > of > images. The thumbnail model cannot process this large number of images > without > a database and is getting slower and slower. > > Maik > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
