deepseek-ai/DeepSeek-V3

Fork 0

mirror of https://github.com/deepseek-ai/DeepSeek-V3.git synced 2026-11-05 00:47:48 +00:00

[GH-ISSUE #1061] [BUG] Deepseek chat website OOM after short usage / 聊天网页短期使用后出现内存溢出（OOM）问题 #653

New issue

Closed

opened 2026-10-26 21:24:52 +00:00 by bsakaguchi · 5 comments

bsakaguchi commented

2026-10-26 21:24:52 +00:00

Owner

Originally created by @tbui17 on GitHub (Dec 21, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-V3/issues/1061

Describe the bug
When using Deepseek chat with lengthy chat history, you get OOM error very quickly. Memory leak issue.

To Reproduce

Have many (1000+) conversations in history
Switch conversations 10-15 times or enter 2-3 chat messages
Browser freezes

Expected behavior
Deepseek should not OOM with a long conversation history.

Screenshots
N/A

Additional context

In chrome/msedge debugger, source file collect-rangers-v5.2.1.js contains a logger that stores events in a map. User accounts have 10,000-100,000 objects. New account has ~15 objects.
- Overriding the source file by removing all code fixed the issue and dropped tab RAM usage from ~3-6 GB to 125 MB.
Thank you for all the hard work

我已使用大语言模型（LLM）翻译此文。如有任何错误，敬请谅解。

错误描述
在使用 Deepseek 聊天功能时，若聊天记录较长，系统会很快出现内存溢出（OOM）错误。疑似存在内存泄漏问题。

重现步骤

在历史记录中拥有大量（1000条以上）对话
切换对话10-15次或发送2-3条聊天消息
浏览器冻结

预期行为
Deepseek 应能处理长对话历史记录，不应出现内存溢出问题。

屏幕截图
无

补充信息

在 Chrome/Edge 调试工具中，源文件 collect-rangers-v5.2.1.js 包含一个将事件存储在映射（Map）中的日志记录器。用户账户中存在10,000至100,000个对象，而新账户仅有约15个对象。
- 通过覆写该源文件并删除其所有代码后，问题得以解决，且标签页内存占用从 ~3-6 GB 降至 125 MB。
感谢你们付出的辛勤努力

Originally created by @tbui17 on GitHub (Dec 21, 2025). Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-V3/issues/1061 **Describe the bug** When using Deepseek chat with lengthy chat history, you get OOM error very quickly. Memory leak issue. **To Reproduce** 1. Have many (1000+) conversations in history 2. Switch conversations 10-15 times or enter 2-3 chat messages 3. Browser freezes **Expected behavior** Deepseek should not OOM with a long conversation history. **Screenshots** N/A **Additional context** - In chrome/msedge debugger, source file collect-rangers-v5.2.1.js contains a logger that stores events in a map. User accounts have 10,000-100,000 objects. New account has ~15 objects. - Overriding the source file by removing all code fixed the issue and dropped tab RAM usage from ~3-6 GB to 125 MB. - Thank you for all the hard work 我已使用大语言模型（LLM）翻译此文。如有任何错误，敬请谅解。 **错误描述** 在使用 Deepseek 聊天功能时，若聊天记录较长，系统会很快出现内存溢出（OOM）错误。疑似存在内存泄漏问题。 **重现步骤** 1. 在历史记录中拥有大量（1000条以上）对话 2. 切换对话10-15次或发送2-3条聊天消息 3. 浏览器冻结 **预期行为** Deepseek 应能处理长对话历史记录，不应出现内存溢出问题。 **屏幕截图** 无 **补充信息** - 在 Chrome/Edge 调试工具中，源文件 collect-rangers-v5.2.1.js 包含一个将事件存储在映射（Map）中的日志记录器。用户账户中存在10,000至100,000个对象，而新账户仅有约15个对象。 - 通过覆写该源文件并删除其所有代码后，问题得以解决，且标签页内存占用从 ~3-6 GB 降至 125 MB。 - 感谢你们付出的辛勤努力

bsakaguchi

2026-10-26 21:24:52 +00:00

closed this issue
added the
stale

closed-as-stale
labels

bsakaguchi commented

2026-10-26 21:24:53 +00:00

Author

Owner

@chenjunfu2 commented on GitHub (Jan 4, 2026):

I have been troubled by this issue for a very long time, and the official still hasn't fixed it yet. Thank you so much for your solution!
我被这个问题困扰了非常久，官方到现在都一直没有对此进行修复，非常感谢你的解决方法！

@chenjunfu2 commented on GitHub (Jan 4, 2026): I have been troubled by this issue for a very long time, and the official still hasn't fixed it yet. Thank you so much for your solution! 我被这个问题困扰了非常久，官方到现在都一直没有对此进行修复，非常感谢你的解决方法！

bsakaguchi commented

2026-10-26 21:24:54 +00:00

Author

Owner

@chenjunfu2 commented on GitHub (Jan 4, 2026):

I wrote a tamper monkey script through deepseek to automatically remove the JavaScript. Here is the script content for those in need
我通过deepseek写了一个篡改猴脚本，自动移除该js，以下是脚本内容，提供给有需要的人

// ==UserScript==
// @name         DeepSeek网页端内存溢出修复 (DeepSeek Web Version Out Of Memory Fix)
// @description  阻止Deepseek的collect-rangers收集脚本修复内存溢出问题 (Blocks the collect-rangers analytics script on DeepSeek to fix memory overflow issues.)
// @namespace    https://github.com/deepseek-ai/DeepSeek-V3/issues/1061
// @version      1.0.0
// @author       deepseek
// @match        https://*.deepseek.com/*
// @run-at       document-start
// @grant        none
// ==/UserScript==

// 匹配 collect-rangers-vx.x.x.js 格式的所有版本
const TARGET_PATTERN = /collect-rangers-v\d+\.\d+\.\d+\.js/;
const LOG_PREFIX = '[DeepSeek OOM Fix] ';

(function() {
    'use strict';
    console.log(LOG_PREFIX + 'DeepSeek Web Version Out Of Memory Fix Started');

    function checkExistingScripts() {
        var scripts = document.querySelectorAll('script[src]');
        for (var i = 0; i < scripts.length; i++) {
            var script = scripts[i];
            if (TARGET_PATTERN.test(script.src)) {
                console.log(LOG_PREFIX + 'Try Remove Script: ', script.src);
                try {
                    script.parentNode.removeChild(script);// 相比script.remove();兼容性更好
                    console.log(LOG_PREFIX + 'Script Removed!');
                } catch (e) {
                    console.error(LOG_PREFIX + 'Remove Error: ', e);
                }
            }
        }
    }

    if (document.head) {
        checkExistingScripts();
    } else {
        document.addEventListener('DOMContentLoaded', checkExistingScripts);
    }
})();

@chenjunfu2 commented on GitHub (Jan 4, 2026): I wrote a tamper monkey script through deepseek to automatically remove the JavaScript. Here is the script content for those in need 我通过deepseek写了一个篡改猴脚本，自动移除该js，以下是脚本内容，提供给有需要的人 ```js // ==UserScript== // @name DeepSeek网页端内存溢出修复 (DeepSeek Web Version Out Of Memory Fix) // @description 阻止Deepseek的collect-rangers收集脚本修复内存溢出问题 (Blocks the collect-rangers analytics script on DeepSeek to fix memory overflow issues.) // @namespace https://github.com/deepseek-ai/DeepSeek-V3/issues/1061 // @version 1.0.0 // @author deepseek // @match https://*.deepseek.com/* // @run-at document-start // @grant none // ==/UserScript== // 匹配 collect-rangers-vx.x.x.js 格式的所有版本 const TARGET_PATTERN = /collect-rangers-v\d+\.\d+\.\d+\.js/; const LOG_PREFIX = '[DeepSeek OOM Fix] '; (function() { 'use strict'; console.log(LOG_PREFIX + 'DeepSeek Web Version Out Of Memory Fix Started'); function checkExistingScripts() { var scripts = document.querySelectorAll('script[src]'); for (var i = 0; i < scripts.length; i++) { var script = scripts[i]; if (TARGET_PATTERN.test(script.src)) { console.log(LOG_PREFIX + 'Try Remove Script: ', script.src); try { script.parentNode.removeChild(script);// 相比script.remove();兼容性更好 console.log(LOG_PREFIX + 'Script Removed!'); } catch (e) { console.error(LOG_PREFIX + 'Remove Error: ', e); } } } } if (document.head) { checkExistingScripts(); } else { document.addEventListener('DOMContentLoaded', checkExistingScripts); } })(); ```

bsakaguchi commented

2026-10-26 21:24:54 +00:00

Author

Owner

@chenjunfu2 commented on GitHub (Jan 8, 2026):

已发布到脚本网站（I have published it to the script website）：https://greasyfork.org/en/scripts/561569-deepseek%E7%BD%91%E9%A1%B5%E7%AB%AF%E5%86%85%E5%AD%98%E6%BA%A2%E5%87%BA%E4%BF%AE%E5%A4%8D-deepseek-web-version-out-of-memory-fix

@chenjunfu2 commented on GitHub (Jan 8, 2026): 已发布到脚本网站（I have published it to the script website）：https://greasyfork.org/en/scripts/561569-deepseek%E7%BD%91%E9%A1%B5%E7%AB%AF%E5%86%85%E5%AD%98%E6%BA%A2%E5%87%BA%E4%BF%AE%E5%A4%8D-deepseek-web-version-out-of-memory-fix

bsakaguchi commented

2026-10-26 21:24:54 +00:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 9, 2026):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!

@github-actions[bot] commented on GitHub (Feb 9, 2026): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!

bsakaguchi commented

2026-10-26 21:24:55 +00:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 25, 2026):

false

@github-actions[bot] commented on GitHub (Feb 25, 2026): false

bsakaguchi referenced this issue

2026-10-26 21:26:10 +00:00

[GH-ISSUE #1106] long-term memory #690