I remember FM in 1999 and also 1989! It's not likely that Adobe will find and fix this longtime issue soon. But if you haven't reported it to the bug site, and discussed it with tech support, it's worth a try.
A kludgy workaround might be to create a Windows/DOS batch file that launches FM and starts a timer that pops a periodic on-screen reminder to save and close all open FM files, then exits and restarts FM. A second batch file could be made to copy the current project to a backup location, perhaps by invoking one of the FM archiving utilities. Surely some folks on this forum could help write the few lines of code it would take. I haven't written a batch file since the last century. Even then, my best ones were created by a colleague who implemented my pseudo-code for our project. HTH On Mon, Oct 3, 2022, 9:34 AM Bertrand Meyer (SIT) < bertrand.me...@inf.ethz.ch> wrote: > Needless to say I have more than adequate resources (recent Intel > processor, 32 GB of RAM, always up to date with Windows updates etc.) > > > > Prior to the current release I used FrameMaker 2019, and prior to that > FrameMaker 2015. They both had the same behavior. > > > > Before that I used the Windows version 7.x for many years, approximatively > 2002-2015 -- it was quite usable, although it did crash occasionally (with > real crashes, not the kind of freezing I am getting now). > > > > And before that I used FrameMaker on Sun workstations, going back to 1993 > (no typo). It worked quite well. It clearly had a memory leak problem which > meant that it had to be restarted once in a while. > > > > But we are in 2022. > _______________________________________________ This message is from the Framers mailing list Send messages to framers@lists.frameusers.com Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com Send administrative questions to listad...@frameusers.com
