Bug report：Constant large memory footprint

Help
1

Steps to reproduce

Step1: Open Obsidian (Safe mode, default Theme)
LCP over 10 s
CLS over 0.4, over 90% costed by div.view-header-title, div.cm-content.cm-lineWrapping, div.embedded-backlinks, div.status-bar
Step2: Editing
Memory around 800M
Step3: Screen frozen (trigger not found)
Memory over 2G
Console message：
[Violation] ‘setTimeout’ handler took N ms （over 3000+ times in very short time）
[Violation] Forced reflow while executing JavaScript took 32 ms
Sandbox Vault has no violation message some how
Step4: Close & Reopen
Everything repeated…

Did you follow the troubleshooting guide? [Y]

Expected result

Smooth opening with LCP under 1 s
Stable run with 800M memory

Actual result

Slow opening with LCP over 10 s
Screen no responding from time to time

Environment

About Obsidian
Version 1.8.10 (Installer 1.8.10)

SYSTEM INFO:
Obsidian version: v1.8.10
Installer version: v1.8.10
Operating system: Darwin Kernel Version 24.4.0: Fri Apr 11 18:32:05 PDT 2025; root:xnu-11417.101.15~117/RELEASE_ARM64_T8132 24.4.0
Login status: not logged in
Language: en
Insider build toggle: off
Live preview: on
Base theme: dark
Community theme: none
Snippets enabled: 3
Restricted mode: on

RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.

MacOS Sequoia 15.4.1

Screenshot 2025-07-08 at 04.14.42
Screenshot 2025-07-08 at 04.14.42974×1964 206 KB

Additional information

Screenshot attached

2

If it doesn’t happen in the sandbox vault, it is likely a problem with your vault or where it is located.

1 Like
3

Is there any way to locate the problems, like which file or which folder?

4

Where is your vault, the path, currently on disk?

On macOS, in the user folder is a good spot (avoid Desktop and Documents because of iCloud).

So,
/Users/USERNAME/vault-folder/
/Users/USERNAME/ObsVaults/vault-folder/
etc.

Also your debug info lists three enabled snippets. Make sure they are disabled as well (if they aren’t).

1 Like
5

Removed some folders and the problem seemed to be solved.

But it’s strange that the files weren’t suddenly added in the last few days, so why did obsidian suddenly crash without any warning?

6

Perhaps you have some huge markdown file in there somewhere.

1 Like
7

There are some big files, but most were not .md and these file were not created in a day. Why the Obsidian crushed without any pre-alert? Does Obsidian scaned all files not only md?