4 Messages
•
172 Points
Sun, May 13, 2018 4:30 PM
Photoshop: Corrupt Ancestors tag in XMP causing giant file sizes
Users have reported enormously bloated files where the issue appears to be spurious entries in the photoshop:DocumentAncestors XMP tag. I was provided some sample files and found tens of megabytes of data disappeared from each file when I removed that tag.
The file that I was given was created in Photoshop CC 2017 for Windows.
While not absolutely certain, evidence seems to suggest that the corruption is being produced in Photoshop, under conditions that I haven't been able to reproduce. As opposed, for example to it traveling around the internet on infected files (which may well be happening as well)
See this thread in the Adobe user forums https://forums.adobe.com/message/10371400 (my comment is at the bottom as I write this.) Or this thread (look near the bottom) https://forums.adobe.com/thread/2382524?start=40&tstart=0 and this blog post http://prepression.blogspot.com.au/2017/06/metadata-bloat-photoshopdocumentancestors.html
I have the files and would be happy to pass them along to you, along with any help I may be able to provide if you'd like.
(Note that in both those forum threads, users actually discovered the problem when the bad files were incorporated into InDesign or PDF files, but the issue began in image files (the ones I looked at were Tiffs.)
-Carl
The file that I was given was created in Photoshop CC 2017 for Windows.
While not absolutely certain, evidence seems to suggest that the corruption is being produced in Photoshop, under conditions that I haven't been able to reproduce. As opposed, for example to it traveling around the internet on infected files (which may well be happening as well)
See this thread in the Adobe user forums https://forums.adobe.com/message/10371400 (my comment is at the bottom as I write this.) Or this thread (look near the bottom) https://forums.adobe.com/thread/2382524?start=40&tstart=0 and this blog post http://prepression.blogspot.com.au/2017/06/metadata-bloat-photoshopdocumentancestors.html
I have the files and would be happy to pass them along to you, along with any help I may be able to provide if you'd like.
(Note that in both those forum threads, users actually discovered the problem when the bad files were incorporated into InDesign or PDF files, but the issue began in image files (the ones I looked at were Tiffs.)
-Carl
Problems
•
Updated
a year ago
158
4
Helpful Widget
How can we improve?
Tags
No tags available
Responses
max_johnson_7790531
Champion
•
626 Messages
•
14.6K Points
3 years ago
This is a huge problem for shared Creative Cloud Library assets. Any library you subscribe to is saved to a hard-coded directory on your system drive. Any object you add to your library performs a save-as to that directory then syncs to the cloud. Now you can have an object that is literally just a vector box with a gradient applied that is 25mb. Multiply that by 50 for a shared UI library, multiplied by a few different libraries and it adds up fast.
@Adobe, how much does it cost to pump an extra 10-30mb of junk data to and from your cloud every time any user saves a file?
For users this is compounded by the fact that newer versions of photoshop routinely eat 40+ gigabytes of scratch disk. A contractor working from a laptop with 500gb drive is going to start feeling the pinch.
It also floods our source control with useless bytes for every version archived.
1
0
carl_seibert_9r2onokujepy3
4 Messages
•
172 Points
3 years ago
I'm trying to chase my examples back through their lifecycle to find the "patient zero" machine, but the path is proving to be long, running from company to company.
-Carl
2
carl_seibert_9r2onokujepy3
4 Messages
•
172 Points
3 years ago
Are your bad files all TIFFs?
[XMP-xmpMM] History Software Agent : Adobe Photoshop CS5 Macintosh, Adobe Photoshop CS5 Macintosh, Adobe Photoshop CC 2015.5 (Macintosh), Adobe Photoshop CC 2015.5 (Macintosh), Adobe Photoshop CC 2017 (Macintosh), Adobe Photoshop CC 2017 (Macintosh), Adobe Photoshop CC 2017 (Macintosh), Adobe Photoshop CC 2017 (Macintosh)
[XMP-xmpMM] History When : 2016:07:27 12:44:58+09:00, 2016:07:27 12:44:58+09:00, 2016:10:28 12:42:56-05:00, 2016:10:28 12:42:57-05:00, 2017:11:07 11:48:41-06:00, 2017:11:07 11:48:42-06:00, 2017:11:07 11:49:22-06:00, 2017:11:07 11:49:22-06:00
[XMP-xmpMM] History Parameters : from image/jpeg to application/vnd.adobe.photoshop, converted from image/jpeg to application/vnd.adobe.photoshop, from application/vnd.adobe.photoshop to image/tiff, converted from application/vnd.adobe.photoshop to image/tiff, from image/tiff to application/vnd.adobe.photoshop, converted from image/tiff to application/vnd.adobe.photoshop, from application/vnd.adobe.photoshop to image/tiff, converted from application/vnd.adobe.photoshop to image/tiff
0
0
mannequin_haine
1 Message
•
60 Points
a year ago
I tried everything and didnt work. I know absolute nothing about what is getting said, the techy stuff... All metadata just confuses the life outa me, im an artist right?
But there is a simple script... so anyone viewing this post nov 2019... theres hope.
google:
Photoshop/Photoshop-saving-issue-FILES-TOO-LARGE
youll find it on one of the adobe forums :)
0
0