If Nextcloud has more than 200 tasks, the app crashes

[mnbvghw]

I have over 500 tasks on my Nexcloud from thegood.cloud. My account with only 30 tasks works fine. My account with 500 tasks crashes when I try to connect it.

To Reproduce
Steps to reproduce the behavior:

1. Create an Account on thegood.cloud with more than 200 or so tasks
2. Try to connect it to the app

Expected behavior
The app doesn't crash, it just synchronises the tasks.

Desktop:

• Fedora 41 Workstation with Gnome
• Planify Flathub 4.11.6

Thank you for everything: Love your app!

[oktayacikalin]

I've around 477 tasks in 9 lists. My biggest list has about 134 tasks. I also use subtasks. I also have Fedora 41 with Planify 4.11.6. I sync my tasks with my nextcloud instance on pikapods. It does not crash.

When you run Planify from the terminal (e.g. flatpak run io.github.alainm23.planify, does it show something interesting?

Does it open for you at all? Does it freeze and then go out of memory?

[mnbvghw]

It just freezes, see screenshot. I reinstalled it a few times, makes no difference.

The terminal says:

** (io.github.alainm23.planify:2): CRITICAL **: 09:51:03.891: objects_item_get_item_type: assertion 'self != NULL' failed

** (io.github.alainm23.planify:2): CRITICAL **: 09:51:03.891: objects_item_get_completed: assertion 'self != NULL' failed

** (io.github.alainm23.planify:2): Gtk-CRITICAL **: 09:51:03.904: gtk_text_buffer_set_text: assertion 'text != NULL' failed

BEGIN:VCALENDAR
VERSION:2.0
PRODID:+//IDN tasks.org//android-140014//EN
BEGIN:VTODO
DTSTAMP:20241109T113524Z
UID:1101028462251141211
CREATED:20241109T110441Z
LAST-MODIFIED:20241109T113326Z
SUMMARY: redacted
PRIORITY:9
RELATED-TO;RELTYPE=PARENT:1088466179837920697
END:VTODO
END:VCALENDAR

and then it lists alot of the tasks like here until it just stops. It still uses a lot of CPU Power and Memory, but nothing happens.

[oktayacikalin]

Creating bigger lists in the GUI takes some time and the app will allocate more memory. You should be able to see that bump in ram allocation relatively fast.

But when it just consumes CPU and nothing else seems to happen, it might be an endless loop in your task dependencies.
I had that happen when moving tasks around in aCalendar+ on Android. I then exported every list, deleted them in Nextcloud and re-imported them using the web UI of the calendar app. The important step was the export using a different app, which would rewrite each task during the export. When I tried the same using the Nextcloud Calendar app, it would not fix my dependency loops, rather exporting the raw data.

Does your today view within the Nextcloud calendar app work?

How many lists do you have within your 500-tasks-account?

In order to identify the broken list, you could delete it within the Nextcloud calendar web app, reconnect planify so that it fetches everything again, and restore/undelete the list again (NC calendar app has a trashcan). This is how I narrowed my faulty lists down.
Please be extra careful when doing this maneuver! DO NOT EMPTY YOUR TRASHCAN AT THIS TIME OR ALL TASKS WILL BE DELETED! You want to try this using a test-list first.

You initially said that it would crash, but it rather sounds like it "never finishes", right? I mean, I cannot see a segfault or something within your output.

[mnbvghw]

Thank you very much for your detailed tips. I still don't know what the problem was, but I took it as an opportunity to delete old tasks (I still had 3000 completed ones) and simply start a new list with a new provider. The app works great, thank you!