Just found out that the large CPU and memory use only happens when the text editor window is open. Otherwise adding thousand or so lines works fine. Interestingly I can then still undo each of the thousand lines by opening the window after they were inserted, so the undo mechanism is working per se.
P * Sebastian Shader via Pd-list <pd-list@lists.iem.at> [2023-04-26 23:44]: > Seems like the fix should already be in 0.54.afaict you can use the 'clear' > or 'set' messages to set the dirty flag to 0, which will clear the undo > history.but I'm also wondering if the text window actually has to exist to do > so, since 'peer' text objects are possible.. > > -seb; > > On Wednesday, April 26, 2023 at 09:25:05 AM PDT, IOhannes m zmölnig > <zmoel...@iem.at> wrote: > > Am 26. April 2023 18:03:16 MESZ schrieb "Peter P." > <peterpar...@fastmail.com>: > >Hi list, > > > >upon trying to add 1000 lines with [until] and [text insert] Pd/wish use up > >all RAM > >(and swap space) on my 8GB Debian box. Is there a way to predict memory > >usage for lines added? What would be the best strategy to do so without > >locking up Pd? > > > > If wish is eating up the memory, then it's most likely due to the internal > "undo" handling of the text-editor. > If so, there's been an issue on GitHub about that, and I think there's also a > fix... > > > mfg.sfg.jfd > IOhannes > > > _______________________________________________ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list > > _______________________________________________ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
