Memory use ramps up after saving > crash Topic is solved
Moderator: abstr
Re: Memory use ramps up after saving > crash
Dan
Honestly I didn't even see that setting - but now changed and I will let you know in due course.
Thanks a lot.
Jon
Honestly I didn't even see that setting - but now changed and I will let you know in due course.
Thanks a lot.
Jon
Re: Memory use ramps up after saving > crash
7.3 will include an HTML comments plugin that does not require any processing during export and which produces comments smaller in file size, so I hope we can keep you limping along until then...
Re: Memory use ramps up after saving > crash
Dan
That's great, thanks a lot. It's only my impression but the lists seem to switch more 'instantly' now, perhaps that's a spinoff from this setting change?
Jon
That's great, thanks a lot. It's only my impression but the lists seem to switch more 'instantly' now, perhaps that's a spinoff from this setting change?
Jon
Re: Memory use ramps up after saving > crash
Dan - update: No crashes so far so that tweak removing the RTF/Word setting seems to have worked.
Thanks,
Jon
Thanks,
Jon
Re: Memory use ramps up after saving > crash
Good news, though I'm left wondering what the problem was...
Re: Memory use ramps up after saving > crash
I jinxed myself! After opening a couple more lists it crashed after save again after a couple of hours' work.
I wasn't using the logger this time but I attach some random process info (I don't know what it means but assume you can spot any unusual activity...) - You can see I saved only a few mins before the crash with no problem and similar memory etc. I'm not doing anything very clever or taxing atm, it's just entering text, moving items around, setting priorities/dates etc.
One point might be that while lists are saved ok, the 'status' of the TDL system is lost - i.e. items I have just opened are not reopened on restart (bc the status is only saved on successful exit?) - Is that all controlled via .ini file?
Another is my primary list is now 5.5MB, I keep meaning to housekeep but never have the time. But maybe now I should slim it down?
Thanks!
Jon
I wasn't using the logger this time but I attach some random process info (I don't know what it means but assume you can spot any unusual activity...) - You can see I saved only a few mins before the crash with no problem and similar memory etc. I'm not doing anything very clever or taxing atm, it's just entering text, moving items around, setting priorities/dates etc.
One point might be that while lists are saved ok, the 'status' of the TDL system is lost - i.e. items I have just opened are not reopened on restart (bc the status is only saved on successful exit?) - Is that all controlled via .ini file?
Another is my primary list is now 5.5MB, I keep meaning to housekeep but never have the time. But maybe now I should slim it down?
Thanks!
Jon
Re: Memory use ramps up after saving > crash
Yes, all state is stored in the ini file and I don't save it very often for performance reasons.
Can you list which of the task views you use? eg. Task Tree, Gantt Chart, etc
Can you list which of the task views you use? eg. Task Tree, Gantt Chart, etc
Re: Memory use ramps up after saving > crash
Dan
The views sadly mostly tree from day to day. A bit of list for housekeeping etc. But I am just trying to align my thinking with gantt and kanban and weekly planner and calendar...
The views sadly mostly tree from day to day. A bit of list for housekeeping etc. But I am just trying to align my thinking with gantt and kanban and weekly planner and calendar...
Re: Memory use ramps up after saving > crash
I ask because some of the other views are less mature.
BTW, have you got auto-save turned on to avoid loss of work while we investigate this?
BTW, have you got auto-save turned on to avoid loss of work while we investigate this?
Re: Memory use ramps up after saving > crash
ps. Can you make sure you always have logging enabled (add -g to the commandline) just in case it offers something useful?