Skip to main content
Mark_Bench
Participating Frequently
September 28, 2017
Question

After installing Update 2 for FrameMaker 2017 keeps crashing... why?

  • September 28, 2017
  • 4 replies
  • 1125 views

I increased substantially the amount of virtual memory on my machine, and that reduced the frequency of crashes, but FM 2017 keeps crashing.

This topic has been closed for replies.

4 replies

Matt-Tech Comm Tools
Community Expert
Community Expert
October 16, 2017

Since you have 8Gb of physical RAM, try turning off the virtual memory option. I've had trouble with it in the past.

-Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant
Mark_Bench
Participating Frequently
October 16, 2017

Hello,

I just added 8 GB more of RAM to my machine last Friday (for a total of 16 GB), and I did switch to “Automatically manage paging file size for all drives” instead of having a “Custom size” assigned.

I will try it this way for a week or so, then I can tell you if it did work or not.

Thank you,

Robert

Matt-Tech Comm Tools
Community Expert
Community Expert
October 11, 2017

Just making sure we're on the same page here...

If you have a virtual machine running Windows 7 Enterprise 64-bit, then (according to some sources) Windows itself is taking up about 20Gb of that virtual disk, leaving you little room to install apps, files, and actually run Windows and Fm.

In case that's you're issue, here's a thread from vmware regarding virtual disk size

Is this a reasonable Windows 8.1 VM size? |VMware Communities

I keep my virtual disk at 75 Gb, and run almost nothing but TCS apps on it. I manage to keep about 20% free disk space. If you have trouble keeping more than 10% free disk space, you need to increase your virtual disk space.

With 224Gb free on your physical drive, you have some room to increase your VM allocation to give it room to breathe.

-Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant
Mark_Bench
Participating Frequently
October 11, 2017

No, I am not running a Virtual Machine. I was referring to Virtual Memory (disk space used as RAM for paging, large documents in this case).

Yes, I am running Windows 7 Enterprise 64-bit, on a Lenovo with Intel Core i5-3570 CPU @ 3.4 GHz, 8 GB RAM.

The local drive C: has 224 GB of free space (not counting the 32 GB allocated for Virtual Memory), and as I mentioned before, all my files reside on a local server which has 207 GB of free space, out of a total of 2.5 TB.

Thanks.

P please don't print this e-mail unless you really need to.

Matt-Tech Comm Tools
Community Expert
Community Expert
October 10, 2017

Even 64Gb may be slim, depending on what else you're doing on the VM. How much free space do you have on your C drive?

Also,check this thread for another (rare?) possible corruption

FrameMaker 9 won't open

-Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant
Mark_Bench
Participating Frequently
October 10, 2017

I have 224 GB of free space on the local C: drive, about half of the total.

All of my files reside on a local server, which has 207 GB of free space of a total of 2.5 TB.

Thanks for the reference. I’ll try that avenue.

P please don't print this e-mail unless you really need to.

Matt-Tech Comm Tools
Community Expert
Community Expert
October 2, 2017

Try renaming your prefs file in your Roaming directory to something like this

C:\Users\Matt\AppData\Roaming\Adobe\FrameMaker\14-prev

Fm will recreate the 14 directory, and if the problem was a corrupted prefs file, you're back in business.

You might also look for issues related to the Linguistics folder (different directory, but sounds like it might be the culprit as well)

-Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant
Mark_Bench
Participating Frequently
October 2, 2017

I renamed the preferences file to '14-old' which helped reducing the frequency of crashes, but unfortunately, FM 2017 keeps crashing.

Matt-Tech Comm Tools
Community Expert
Community Expert
October 2, 2017

I noticed you mentioned virtual memory, is this on a VM machine?

If so, the "size" of the VM ("hard disk"), the number of processors, and the amount of RAM allocated will all play a part.

-Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant