Over the years I have had insurmountable problems with FrameMaker version 5.5.6, 7, and 8 freezing exactly 60 minutes after FrameMaker startup on certain machines, including Dell, Lenovo and Asus hardware, and Windows XP and Windows 7 operating systems. At the 60 minute mark exactly, the FrameMaker process hammers the CPU up to 50% and stays there, and the program is then frozen ( " not responding " ). The rest of the system is still functioning. I (and several system administrators) have spent many days trying everything in the book, to no avail. I never found the source of the problem; I gave up and avoided it by using random Windows machines that don't exhibit the problem, and by using FrameMaker on Solaris. I am working at home now (actually, *trying* to work at home); I can no longer avoid the problem, and the lock-ups make FrameMaker practically unusable.
Although I appreciate any suggestions, each one takes 60 minutes to test (obviously) and I have tried so many that I feel like I can't try any more of them without some kind of a lead. To that end, I have a direct question to the Adobe FrameMaker programmers:
WHAT IS FRAMEMAKER DOING AT THE 60 MINUTE MARK?