debug.log: a Bug in Chrome and Edge Creates This File on the Desktop

The desktop is often one of the most personal parts of a computer. In it we can put the background we want, place the icons of our most used programs, and place them where we want. For this reason, any strange or unwanted element on this desktop will immediately catch our attention And this is what has happened to users who have encountered, in recent days, a mysterious file, debug.log, in their desk.

Many Windows users, especially those using Chrome, Edge, or any other Chromium- based browser , have suddenly found that, overnight, a mysterious file, called debug.log, appeared on their desktop that they didn’t. had created. It is not the first time that this file, which should not be here, has appeared on the desktop. And luckily, you have an easy solution.

debug.log: a Bug in Chrome and Edge

A recently seen bug in Photoshop

Just over a month ago, Photoshop users found that when they opened their image editing program, a debug.log file would appear on their desktop. This file recorded an error when loading a JS library detected while the program was running, and it was blocked while the Adobe software was open. If the file was deleted, when Photoshop was reopened, it would reappear. And so on.

Archivo debug.log Photoshop

The latest versions of Photoshop, thankfully, have fixed the problem. However, there are users who are finding themselves again with this file, although this time those responsible are Chrome, Edge and any web browser based on Chromium.

The file “debug.log” of Chrome and Edge

A significant number of Chrome and Firefox users have found this file suddenly starting to appear on their desktop. When we open it, all we can see is a line with a message ” FindFirstFile: The system cannot find the path specified “, which basically indicates that the system could not find a specific PATH.

After a long investigation, it has finally been discovered that this is a localized problem in the Chromium rendering engine, and therefore affects all browsers that use it, such as Chrome, Edge, Opera and Brave, among others. . It does not affect users who are still using the classic version of Edge.

This bug has been logged in both the Edge community forums and the Chrome bug list for over a month, though it didn’t start to affect users massively until the arrival of Chromium version 86 earlier. of this month.

How to fix the error so that this file does not appear again

If we already have this file on our desktop, and we don’t care if it is there, then we don’t have to do anything. It is a very small, harmless file that does not affect the proper functioning of the PC or the browser at all.

However, if we are one of those who want to have everything in order, and we do not want an unnecessary file to roam our desktop, then we simply have to follow a few simple steps. We have to go to the “Crashpad” directory of each browser. To do this, we will write the following path in the address bar of the file explorer:

If we use Google Chrome:

%localappdata%/Google/Chrome/User Data/Crashpad

For Microsoft Edge:

%localappdata%/Microsoft/Edge/User Data/Crashpad

Once we have this folder open, what we will have to do is delete all its content. We do not have to worry, as doing so will not cause the PC to malfunction or affect the operation, or our data, of Chrome or Edge.

After deleting all the files in this folder, we restart the computer. Ready. From now on, when we use Chrome or Edge again, this file will no longer appear on our desktop.