Skip to main content
Mefix
Mefix
Inspiring
September 11, 2018
Answered

Cloud Libraries broken since last update - Photoshop 19.1.6

  • September 11, 2018
  • 3 replies
  • 1511 views

Last update of Adobe photoshop introduced a bug with Cloud Libraries that makes them unusable.

After a few searches the entire panel becomes unresponsive, takes minutes to process search queries and stops showing thumbnail previews.

Video of the repro here:  Screencast - Cloud Libraries bug - 21-20 10-09-2018 https://monosnap.com/file/zJm9Jds2oVRaGynjBWjHYmiNAgBh4k

A fix for this is killing the "Adobe CEP HTML Engine" process after EACH search query, which restarts the library panel.

We have switched our organization to use Cloud Libraries in our pipeline, and this update basically killed it.

    This topic has been closed for replies.
    Correct answer Mefix

    Update for those affected.

    I've started another topic in the family section of the forums where you can read more about the bug's journey. - https://feedback.photoshop.com/photoshop_family/topics/cloud-libraries-broken-since-last-update-photoshop-19-1-6?rfm=1&topic_submit=true

    Thanks to the Engineering Department of Adobe Creative Cloud Libraries, we've been able to debug and figure out the problem.

    Back in beginning of September Cloud Libraries have switched their method of thumbnail generation from server side to client side. This unearthed a very old Adobe bug where some files would be saved with gigantic amounts of trash metadata, bloating the size of files that should be 40kb to over 30mb (There are several topics for this on the forums). If you try and open those metabloat files in chrome (which cloud libraries use in their panel), it would take about 30+ seconds to open. This made the panel lag very badly and search queries taking up minutes at a time as a result.

    Now all the thumbnails that the Cloud Libraries panel have generated could have been affected by the metabloat, mind that only some files are affected.

    You can browse the thumbnails in the C:\Users\[username]\AppData\Roaming\Adobe\Creative Cloud Libraries\LIBS\[hash]_AdobeID\creative_cloud\renditions folder. Search for overly large files to see if you're affected.

    Until Adobe implements a fix for the thumbnail generator, you can use optimization tools to make the thumbnails smaller (Like PNGGauntlet). If you have a lot of libraries, you can use a small script file we've made for our team to optimize all the files at once:

    Linky: File “tools.zip”

    Drag your renditions (Contains png files) and dcx (contains psd and some png files) folders over the removemetadata_all.bat file and leave it working. If you have a lot of files this can take a while. I had 11058 files across 56 libraries with unoptimized thumbnail size of 7.5GB that was optimized to 564 MB

    So far it's unknown if this temp fix is sustainable as we don't know how often thumbnails are regenerated. New items in libraries will need to be checked for metabloat as well to retain consistency. But at least the libraries are usable once again. Hurray.

    dcx

    3 replies

    Mefix
    MefixAuthorCorrect answer
    Inspiring
    November 12, 2018

    Update for those affected.

    I've started another topic in the family section of the forums where you can read more about the bug's journey. - https://feedback.photoshop.com/photoshop_family/topics/cloud-libraries-broken-since-last-update-photoshop-19-1-6?rfm=1&topic_submit=true

    Thanks to the Engineering Department of Adobe Creative Cloud Libraries, we've been able to debug and figure out the problem.

    Back in beginning of September Cloud Libraries have switched their method of thumbnail generation from server side to client side. This unearthed a very old Adobe bug where some files would be saved with gigantic amounts of trash metadata, bloating the size of files that should be 40kb to over 30mb (There are several topics for this on the forums). If you try and open those metabloat files in chrome (which cloud libraries use in their panel), it would take about 30+ seconds to open. This made the panel lag very badly and search queries taking up minutes at a time as a result.

    Now all the thumbnails that the Cloud Libraries panel have generated could have been affected by the metabloat, mind that only some files are affected.

    You can browse the thumbnails in the C:\Users\[username]\AppData\Roaming\Adobe\Creative Cloud Libraries\LIBS\[hash]_AdobeID\creative_cloud\renditions folder. Search for overly large files to see if you're affected.

    Until Adobe implements a fix for the thumbnail generator, you can use optimization tools to make the thumbnails smaller (Like PNGGauntlet). If you have a lot of libraries, you can use a small script file we've made for our team to optimize all the files at once:

    Linky: File “tools.zip”

    Drag your renditions (Contains png files) and dcx (contains psd and some png files) folders over the removemetadata_all.bat file and leave it working. If you have a lot of files this can take a while. I had 11058 files across 56 libraries with unoptimized thumbnail size of 7.5GB that was optimized to 564 MB

    So far it's unknown if this temp fix is sustainable as we don't know how often thumbnails are regenerated. New items in libraries will need to be checked for metabloat as well to retain consistency. But at least the libraries are usable once again. Hurray.

    dcx

    Mike_Gondek10189183
    Community Expert
    Mike_Gondek10189183Community Expert
    Community Expert
    September 17, 2018

    Good to see someone using cloud libraries with so many assets, sorry to hear the panel becomes unresponsive.

    Looks like you did a great job naming your assets, just doublecheck you do not have any backslashes or colons in the asset name. As this causes problems in layer comps, for the same reasons would avoid atleast those 2 characters in naming anything Adobw uses.

    Take a look at how your adobe cloud application is doing, as that links into your libraries. You can rest the OOBE as per solution #5.

    Adobe Creative Cloud desktop app doesn't open or shows a spinning progress wheel  even if you do not have a spinning wheel as this can clear up a corrupted .db.

    Mefix
    MefixAuthor
    Inspiring
    September 19, 2018

    Hi Mike,

    I've removed any and all : and / symbols from the libraries (some were added over 2 years ago) and followed the OOBE guide

    Unfortunately, this did not help, after rebuilding the database, the same behavior persists.

    The sync took an hour or so File “l5p38i7aoyipf9fuphnub0gvgdkhg7tb8646ldp8fh7d88mkqa.png”

    Current library stands at 121GB spanning about 6 projects File “ibuef6hh8lz0ttumhsvxunez7x28a2d37u6sk4y4n8wfx63hmj.png” with a total of about 64 libraries.

    Fun fact: Theres a limit of 1000 files per library, we had to split the icon library into 2 volumes

    Hey Adobe, lets make a case with you for your next expo!

    Mike_Gondek10189183
    Community Expert
    Mike_Gondek10189183Community Expert
    Community Expert
    September 19, 2018

    HI Mefix,

    Has anyone else out there used libraries to the extent of reaching the 1000 limit files per library, your feedback could be very helpful to Mefix.

    Thanks for sharing the 1000 limit on libraries, did you get an error message to find that out?  I have not noticed any posts on forums exactly as yours, but suspect on average  people do not use libraries to the extent you are, but applaud you for

    being adventurous and innovative.

    We did have errors about the libraries not loading which might have some good ideas for you.

    Solution to the issue: Adobe Creative Cloud Libraries panel doesn't load in desktop products

    Does searching current library work  better

    than searching for all

    I understand you may need to search all, but trying to learn what exactly causes the non-responsiveness occur.

    A
    Anonymous
    September 11, 2018

    Hi

    You can report bugs over here

    Photoshop Family Customer Community

    You can also roll back to a previous version of Photoshop to see if that helps

    Mefix
    MefixAuthor
    Inspiring
    September 11, 2018

    Afraid not, reverting back to version 19.1 still produces the same behavior, as if the fault lies in the HTML caching engine on adobe side.

    Edit, went back as far as 2015.5 version - same faulty behavior across all adobe products on mutiple machines.

    Mefix
    MefixAuthor
    Inspiring
    September 17, 2018

    Up.

    As more people are updating to the latest version of Photoshop in our organization, the more people who use libraries on a daily basis encounter this problem.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices