Fixed: Photoshop creating a debug.log file when you open a PSD File

[BoyMatik]

I just updated my photoshop to the latest version, 21.2.2.289, and I noticed that everytime I open a PSD file. Photoshop creates a debug.log file in the same folder as the PSD file. How do I turn this off?

[Moderator note: PS-55193]

[Guest]

Hi

Not seeing the issue here with version 21.2.2, did you open the log file to see what information it contains

[BoyMatik]

I did open it, it opened in Notepad and it was just empty. 

[boneadventure]

This file is created every time I open psd, jpg, etc. through windows explorer, but only if the program has not been launched before. If you start Photoshop first and then double-click the file, or if you use the "edit original" function on the linked file in Illustrator or InDesign, the debug.log is not generated.

Every time 3 lines are added to it:

[0817/194909.990:WARNING:angle_platform_impl.cc(52)] compileToBinary(230):
C:\fakepath(57,8-58): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(65,8-28): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them

[Gilad Koriski]

The same exact thing here, same values and all.

[Peter5FC2]

I also have 21.2.2 and experiencing this, getting a debug file in the same folder where the image is saved. Below is the the content of the log file but I am not sure if it's the same one all the time.

[0821/112231.376:INFO:CONSOLE(1)] "Long rAF frame-time", source: file:///C:/Program%20Files/Adobe/Adobe%20Photoshop%202020/Required/www-rich-tooltips/build/external.js (1)
[0821/113833.475:ERROR:media_internals.cc(112)] Cannot get RenderProcessHost

[Pixanne Photographies]

C'est la même chose pour moi 😞 Same for me

Debug Bloc note

[0910/173706.514:INFO:CONSOLE(1)] "Long rAF frame-time", source: file:///C:/Program%20Files/Adobe/Adobe%20Photoshop%202020/Required/www-rich-tooltips/build/external.js (1)

[Margy82]

Same here. From the last update every file I open Photoshop create an empty debug.txt file in the same directory of the image opened and this file cannot be deleted until Photoshop is closed.

[AFS Opus]

Same here >>
[0820/073837.435:warning:angle_platform_impl.cc(52)] compileToBinary(230):
C:\fakepath(57,8-58): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(65,8-42): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them

[Christian Lietzke]

Same problem here with a little bit longer error message >>

[0820/074917.085:WARNING:angle_platform_impl.cc(52)] compileToBinary(230):
C:\fakepath(57,8-58): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(65,8-28): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them

[0820/075313.837:INFO:CONSOLE(1)] "Long rAF frame-time", source: file:///C:/Program%20Files/Adobe/Adobe%20Photoshop%202020/Required/www-rich-tooltips/build/external.js (1)
[0820/075313.974:WARNING:angle_platform_impl.cc(52)] compileToBinary(230):
C:\fakepath(69,8-58): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(77,8-28): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them

[Tobias_Soelch]

Same here!

[Stefan Malz]

Same problem here: Open a file by double-click creates a "debug.log" file in that directory.

[Rick W.]

Same here, double-click opening jpg in v. 21.2.2, created debug.log in source folder:

[0820/162342.476:INFO:CONSOLE(1)] "Long rAF frame-time", source: file:///C:/Program%20Files/Adobe/Adobe%20Photoshop%202020/Required/www-rich-tooltips/build/external.js (1)
[0820/162342.671:WARNING:angle_platform_impl.cc(52)] compileToBinary(230):
C:\fakepath(69,8-58): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(77,9-43): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them

[Андрей Шубин]

Same here! But the file is empty.

[andrewl84241848]

Count me in. Mine is empty as well.

[stevent76891219]

My PS started doing the same after the latest update. It doesn't seem to cause any problems, but it may be indicative of a problem with the update. Sometimes the log is empty, sometimes not.

[Adobel]

Here as well.

Similar bug as a few months ago with Acrobat..

[gusnruss]

Since most recent update August 2020 a debug.log appears in the location of the first PSD opened - on the desktop or in a folder.   I'm using Win 10 64 and its Photoshop version  21.2.2 20200807.r.289 2020/08/07: 287d0d87ec x64.  Shouldn't debug files be located in a Photoshop system folder?  

[Guest]

Maybe it's worth reporting it as a bug on the Adobe Feedback Forum and add a link to this thread

[Андрей Шубин]

It's strange, but Photoshop stopped creating the debug file when I installed the previous version of the program. Photoshop 20.0.10

[PacoD]

Today is August 21 2020.
I'm experiencing the same issue, and have been for a few days now. I keep getting alerts from my cloud storage service about "unresolved issue; unable to sync" regarding this debug log file that is (automatically) created everytime I launch PsCC (version 21.2.2 20200807.r.289 2020/08/07: 287d0d87ec x64), and placed in the same folder of whatever Ps file I open...

What gives?
The debug file in question is devoid of content.

[Odairjki]

Adobe caught Microsoft's illness. It is amazing how many bugs and fixes are released. Each update fixes an error and creates another one. In fact, Adobe has not been the same for a long time. I think there is a lack of competition. I miss Photoshop 7 that just worked.

[ampl43110085]

Same here!

"[0821/191223.026:WARNING:angle_platform_impl.cc(52)] compileToBinary(230):
C:\fakepath(57,8-58): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(65,8-27): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them

[Gardis_SE]

I have the same problem! 

[0822/183321.866angle_platform_impl.cc(52)] compileToBinary(230):
C:\fakepath(57,8-58): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
C:\fakepath(65,8-28): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them

[mairi0D4D]

I have the same problem. You can avoid the debug file being created if you open files from Bridge rather than double clicking them.