What I’m trying to do
I am getting this error:
Plugin “todoist-sync-plugin” is not passing Component in renderMarkdown. This is needed to avoid memory leaks when embedded contents register global event handlers.
I want to get rid of it.
Things I have tried
I’ve looked on todoist and the pages where I bring in my todos. I don’t know what this error is telling me; so I don’t know how to go about getting rid of it.
Any explanation and suggestions would be appreciated.
Thanks–
Al
For things like this, I usually go to the plugin’s GitHub page first to see if anything turns up. Maybe this?
opened 08:55PM - 30 May 23 UTC
🐛 bug
**Describe the bug**
I'm not actually sure that this is a bug yet, but Obsidian… itself seems to feel that this could be the source of a potential memory leak.
When the plugin parses a todoist fence in the latest version of Obsidian (1.3.4 as I'm writing this), the following stacktrace is emitted:
```
Error: Plugin "todoist-sync-plugin" is not passing Component in renderMarkdown. This is needed to avoid memory leaks when embedded contents register global event handlers.
at t.render (app.js:1:1255232)
at t.renderMarkdown (app.js:1:1255013)
at eval (MarkdownRenderer.svelte:13:28)
at run (index.mjs:20:12)
at Array.map (<anonymous>)
at eval (index.mjs:2058:58)
at flush (index.mjs:1280:17)
t.render @ app.js:1
```
**To Reproduce**
Steps to reproduce the behavior:
1. Install the latest Obsidian
2. Install this plugin
3. Observe the developer console while opening a page with a <pre>```todoist</pre> fence
**Expected behavior**
No errors in the console.
**Screenshots**

**Desktop (please complete the following information):**
- Plugin Version: **_1.11.1_**
- Obsidian Version: **_1.3.4_**
**Additional context**
N/A
system
Closed
September 16, 2023, 10:23pm
3
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.