[Todoist] Fails with JS heap out of memory error about extensions HOT 5 OPEN

Thank you for opening this issue!

🔔 @AnishDe12020 @kud @casassg @Princeyadav05 you might want to have a look.

from extensions.

Looks like my issue is a duplicate: #10789

So copying over my latest comment from that issue:

The issue has been happening every few days since I initially reported it. Same error logs.

On days where the issue occurs (such as today), reloading the extension will work for a few seconds at best, and then crash again.

Given the error is related to an out-of-memory issue, my theory is that it occurs on days where there are many tasks in my todo list, and doesn't happen on days when there are fewer. But I've not yet been able to validate this theory.

Is there any way to get more detailed logs to see what's going on?

from extensions.

On days where the issue occurs (such as today), reloading the extension will work for a few seconds at best, and then crash again.

Given the error is related to an out-of-memory issue, my theory is that it occurs on days where there are many tasks in my todo list, and doesn't happen on days when there are fewer. But I've not yet been able to validate this theory.

I believe you might be onto something. I have experimented with the task text display limit, which currently is set to 35, but I have also tried settings ranging from 20 to over 40. Additionally, I've tested filtering techniques to display fewer tasks from my typically full to-do list.

Just like you, I haven't been able to fully validate this theory. However, I suspect that the solution to the issue lies in this direction.

from extensions.

I've added a bunch of "test" tasks to my Today list, to see if I can force a crash.
(I was able to clear the crash in my case by reducing the number of tasks in my Today, and clearing the extension's cache)

So far, 110 tasks works fine (with most of those being "test"). But I suspect it's less to do with the number of tasks, and more to do with the amount of memory each task takes up. e.g. a recurring task that has been repeated for several months would take up more memory than a similar task which has never been completed.

I wouldn't expect the task text display limit would affect this bug, as the extension would still need to load the entire task into memory. But I'm not gonna rule that out either. For now, I've set mine to 100 characters, and it's not yet causing any issues.

I'm sure with enough dedication (or automation) I'd be able to force a crash, but so far with these small "test" tasks I've not been able to do so yet.

from extensions.

turns out i can duplicate a whole bunch of tasks in one go.

so with 206 "test" tasks (in addition to the real tasks in my list), I'm able to force a crash.
(This is waaaaay more tasks than I'd normally have. Normally I see the issue at around 50 tasks. but those tasks have more data in them than these simple "test" tasks)

So now that I have a reasonably reliable way to force a crash... if we knew of a good way to get more error logs, then we'd be closer to figuring out how to resolve the issue.

from extensions.