Elements 11 or 12 organizer: Unable to delete a big number of files

  • 1
  • Question
  • Updated 4 years ago
  • (Edited)
With PSE11 or 12 in Win 7 or Vista, I am unable to delete (from catalog) a large number of files. The process takes a long time, then aborts with a message that deleting could not be done.
Watching the task manager, I can see that the Organizer is progressively using more and more ram. The process aborts when the maximum available ram for PSE is reached.
- Is there a reason why so much RAM is used, such as enabling 'undo' feature?
- If yes, would a message with a warning that deleting can't be undone be possible?
- Could it be possible to implement a process in which the batch to delete would be segmented in several chunks?

Deleting many files is required in many situations, such as deleting video files when the backups freeze, or when creating a catalog with only processed files without the originals/raws.

Edit : no change after the Elements 12.1 update.
Photo of Michel BRETECHER

Michel BRETECHER, Champion

  • 1087 Posts
  • 227 Reply Likes
  • frustrated

Posted 5 years ago

  • 1
Photo of Andromeda14

Andromeda14, Employee

  • 105 Posts
  • 7 Reply Likes
Please uncheck all the checkboxes as mentioned on solution #1 on blog: http://psekb.blogspot.in/2013/04/how-...
In addition also quit the ElementsAutoAnalyzer process from activity view.
Please revert if your issue continues.

~Surendra
Photo of Michel BRETECHER

Michel BRETECHER, Champion

  • 1087 Posts
  • 227 Reply Likes
Thanks for the feedback, Surendra.
I am not home now, and what I'll be able to do will be on a Vista 32 bits computer with PSE12.1 in a couple of days.

To summarize my tests on my Windows7 PC, 8 GB, ie5 processor, the same behaviour shows with PSE11, PS12 and PSE12.1.
In all cases, elementsautoanalyzer is not running in the background, and my catalogs are repaired and optimized, and there is enough space in my scratch disks.
The abortion of the process takes place after a relatively long time (more than half an hour to delete 7 000 items form a library of 20 000), after memory usage has slowly gone up to about 3700 MB. I can delete safely batches of 1 000 items.
I'll come back as soon as I have tested on the Vista 32 bits computer (4 GB ram).
Photo of Michel BRETECHER

Michel BRETECHER, Champion

  • 1087 Posts
  • 227 Reply Likes
I have tested the problem with two different computers and softwares:
- Vista 32 bits, two cores, 4 GB RAM - PSE12.1
- Win 7 64 bits laptop, ie5, 4 GB RAM - PSE10

Same results with different catalogs of about 40 000 items, trying to delete 10 000 items. I always have ElementsAutoAnalyzer not running for the tests.
Photo of Surendra

Surendra, Employee

  • 168 Posts
  • 18 Reply Likes
Hi Michel,
Apologies for delayed response.

Have you used same testdata for both PSE10 and PSE12.1?
Analyzing your test results, it seems that the issue is not specific to any version (or ElementsAutoAnalyzer for that matter). I am not aware of any such 'performance issue' but will investigate it on our side.

Meanwhile, you can select all your media (which is to be deleted) and press the 'delete' button at once and leave your system overnight. This will ensure that 'successful' deletion.

~Surendra
Photo of Michel BRETECHER

Michel BRETECHER, Champion

  • 1087 Posts
  • 227 Reply Likes
Thanks for coming back, Surendra.
The test data was from my main running catalog, not necessarily updated (I think I used older versions in some cases). Those catalogs are clean and tested with successful backups and restores.
I also think that the problem is not specific to any version or the ElementsAutoAnalyzer or any recent Elements version. I'll do a test with PSE6 just for curiosity.
Leaving the system overnight does not help. I take care to have no other software running at the same time and also minimal external processes and services. If I look at the Performance tab of the the task bar in Windows, the Organizer uses a growing part of the available memory until the process aborts with the message.
Photo of Surendra

Surendra, Employee

  • 168 Posts
  • 18 Reply Likes
Hi Michel,
I am running out of ideas for your issue. Since this is a performance issue, best way is to let Organizer do what it wants for sometime. Since deleting large number of media (in such a large catalog) is not very frequent, we can safely assume we won't be facing similar issues in future.

~Surendra
Photo of Joseph

Joseph

  • 1 Post
  • 0 Reply Likes
I have a similar issue but with smaller number of photo. When I use the Photo Downloader and before the photos are in the main area with all of my other 30,000 photos I am deleting photos from the Photo Downloader. The number of photos to be deleted is around 1500 out of 1600 in the Downloader. I am running 8 gigs memory and a GeForce GTS450. It has been suggested that doubling the gig to 16 and/or increasing the speed of the GeForce might solve this issue. Any thoughts on this proposal???
Photo of Surendra

Surendra, Employee

  • 168 Posts
  • 18 Reply Likes
Hi Joseph,
Michel's issue was deletion from main grid while your's is deletion from Photo downloader. They are not the same.
How are you deleting the photos from Photo downloader?

Regarding increasing your RAM size, if you are running PSE version older than PSE13, then it won't be of significant help because PSE12 (or older) was 32 bit based application. Hence there are some limitations on the maximum RAM it can use. Is this (deleting large number of images) a regular workflow of yours?

~Surendra
Photo of Michel BRETECHER

Michel BRETECHER, Champion

  • 1085 Posts
  • 227 Reply Likes
Joseph,
If you are selecting and culling from the downloader, I'd suggest using another workflow in 3 steps:
1- copy your photo shoot batch to a second empty card
2- do the sorting/culling from your OS (explorer/Finder)
3- use the downloader to import from the second card

Advanges :
- much quicker
- originals are safe on the original card
- no risks of importing duplicates
- you still have the advantages of the advanced mode of the downloader: renaming, storing in the default date folder structure, assigning metadata template...