obsidian-plugin/mnaoumov_obsidian-advanced-debug-mode
1
0
Fork 0
mirror of https://github.com/mnaoumov/obsidian-advanced-debug-mode.git synced 2026-07-22 05:44:00 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
mnaoumov_obsidian-advanced-.../demo-vault/04 Long running tasks.md
Michael Naumov 715fe7ed5b feat: add demo vault 
Add a developer-focused demo vault that shows how Advanced Debug Mode enriches
the DevTools console. Notes are numbered basic to advanced and cover debug mode,
long stack traces (with a Run button that throws through async boundaries), async
long stack traces, long-running-task timeouts, mobile DevTools, debug namespaces,
and every setting. A no-app integration suite keeps the notes in sync with the
PluginSettings surface. The root README documents the three ways to open it.
2026-07-20 09:19:21 -06:00

1.4 KiB
Raw Permalink Blame History

Docs

Long running tasks

Obsidian guards some internal operations with timeouts: if a task takes too long, Obsidian assumes it has hung and aborts it. That is sensible in normal use, but it fights you while debugging - the moment you pause on a breakpoint and inspect state for a few seconds, the timeout fires and the task you were tracing is torn down before you can finish.

Advanced Debug Mode lets you relax those timeouts while you debug.

The settings involved

  • shouldTimeoutLongRunningTasks - leave this on for normal use, and turn it off before a debugging session so tasks are allowed to run (or pause) indefinitely.
  • shouldIncludeTimedOutTasksDetails - when a task does time out, include extra details about it in the console so you can see which task was aborted and why.

Both live in Settings -> Community plugins -> Advanced Debug Mode and are documented in 06 Settings.

Typical workflow

  1. Open Settings -> Community plugins -> Advanced Debug Mode and turn Timeout long running tasks off.
  2. Set your breakpoints in DevTools and reproduce the slow operation - it will now wait on your breakpoints instead of being aborted.
  3. When you are done, turn the setting back on so Obsidian's normal safety timeouts are restored.

Leaving timeouts disabled outside a debugging session is not recommended - a genuinely stuck task would then hang instead of recovering.