本地运行网页时Chrome自动生成Debug.log文件问题求助

Hey there! Let's figure out why Chrome keeps spitting out that annoying Debug.log file every time you open your index.html—especially since other browsers don't do this, and it doesn't break your site.

First, let's understand the root cause #

Your code uses a <FRAMESET> structure, which is an old HTML4 feature that's been deprecated in HTML5. Chrome tends to be more verbose about handling outdated web standards, and it's likely generating this log as part of its debugging/legacy support for framesets when accessing local files (via the file:// protocol).

Here are 3 solutions to stop the Debug.log from appearing: #

1. Replace the deprecated frameset with modern HTML/CSS

Framesets are no longer recommended, so switching to a more modern layout (like using iframes with flexbox) will not only fix the log issue but also make your site more future-proof. Here's a drop-in replacement for your code:

<!DOCTYPE html>
<html>
<head>
    <title>Frames</title>
    <style>
        * { margin: 0; padding: 0; box-sizing: border-box; }
        body { display: flex; height: 100vh; }
        .frame-container { overflow-y: auto; }
        #left-frame { width: 20%; }
        #main-frame { width: 80%; }
        iframe { width: 100%; height: 100%; border: none; }
    </style>
</head>
<body>
    <div class="frame-container" id="left-frame">
        <iframe src="menu.html" name="left"></iframe>
    </div>
    <div class="frame-container" id="main-frame">
        <iframe src="start.html" name="main"></iframe>
    </div>
</body>
</html>

2. Check Chrome's debug logging settings

Sometimes Chrome might have hidden logging enabled that's generating this file:

• Open Chrome DevTools (press F12 or Ctrl+Shift+I)
• Click the gear icon in the top-right corner to open Settings
• Navigate to the Console section, then look for options like "Preserve log" or "Enable verbose logging"—uncheck any that might force log saving to a file
• Also, check Chrome's desktop shortcut: right-click it, go to Properties, and make sure there are no extra launch flags like --enable-logging or --v=1 in the "Target" field (these force Chrome to generate debug logs)

3. Serve your files via a local web server instead of file://

Chrome handles local files differently than files served over HTTP. Using a simple local server can bypass the file:// protocol quirks that trigger the log:

• If you have Python installed, open a terminal in your website folder and run:

  # For Python 3
  python -m http.server 8000
  # For Python 2
  python -m SimpleHTTPServer 8000
  

• Then open Chrome and go to http://localhost:8000/index.html—this should prevent the Debug.log from being created

Final note #

The frameset approach is really outdated, so going with option 1 is the best long-term fix. It'll eliminate not just this log issue but also potential compatibility problems with future Chrome updates.

内容的提问来源于stack exchange，提问作者Vangelis Dingelidis