Skip to main content
O
ohne_hosen
Inspiring
February 10, 2017
Question

FrameMaker 2017 Constantly Crashing

  • February 10, 2017
  • 4 replies
  • 3161 views

Just trying to set up FM 2017; while trying to set up EDD rules for my output templates, FrameMaker is crashing constantly.

Usually all it takes to cause a crash is trying to scroll through structured view or expanding a collapsed tag or structure item.

Sometimes the crash is so bad that I have to restart my computer to get the FM processes to actually stop.

I sent all of the crash logs to fmerror@adobe.com but the message bounced.

Anything I can do? I'm currently on a 30-day trial so I can get it set up before my boss(es) pony up for licenses. I got FM11 working successfully at my previous company so I really talked it up at this new place. Not making a great first impression here, though...

Edit to add: I have tried uninstalling and reinstalling FM2017. I have also noticed that the crashes tend to happen with the referenced sections of EDDs. I can open the modules without too much trouble.

This topic has been closed for replies.

4 replies

D
deanf94458202
Participant
October 16, 2018

UPDATE:

My above workaround was not effective and FrameMaker 2017 continues to crash regularly.

AJIT_M
AJIT_M
Inspiring
October 16, 2018

Hi,

I have sent you a private message. Please try the suggested steps and incase that doesn't work, then provide the requested details so that we can connect and look into the issue.

Regards,

Ajit

P
pavandg
Participant
January 30, 2019

Hi Ajit,

FrameMaker 2017 is crashing constantly on my system when I select a chunk of text.

If you want, I can share the log.

Please have a look and do the needful.

Regards,

Pavan

D
deanf94458202
Participant
September 25, 2018

I am having the same problem (with FM 2017 Release, 14.0.4.511):

FrameMaker crashes (approximately once per hour - three times this afternoon so far) simply with routine 'cut and paste' use.

Please advise.

D
deanf94458202
Participant
September 25, 2018

FYI,

I have a suspicion that the crashes I am experiencing occur when working directly from our local network and is related to the total length of the path name and graphic file names exceeding the MS Windows maximum limit of 256 characters.

As a workaround, I will work with my FM files from my local 'C:\' for the time being and will endeavour to keep the length of my file names to a minimum. I hope this will resolve the issues.

C
CTAS
Participating Frequently
May 6, 2017

I am having crashing issues also, can't launch it and Tech Support has uninstalled and reinstalled on my computer 3 times now and it's happening again. Can't open files so I can save down to 2015.

Why does this keep happening?

O
ohne_hosenAuthor
Inspiring
May 8, 2017

2017 seems like a very buggy release. It crashes sometimes if I select too much text, it crashes during output, it breaks cross-references, it doesn't seem to process EDD formatting correctly (I thought I had it fixed with a rule change but it still doesn't work), etc, etc, etc....

I installed the update a week or so ago but it doesn't seem to have fixed anything. I'm sort of up and running but still dealing with frustrating issues that I didn't have with the last version of Frame I used (11), and I wish I had an older version to save down to, but I don't.

Hoping that the next update eases some of this pain.

Viku
Adobe Employee
Viku
Adobe Employee
May 9, 2017

Hi Ohne,

I have sent you a private message with my email address. Kindly email me your contact details. We will get back to you.

Regards

Viku

Adobe Systems

K
Adobe Employee
ksaini
Adobe Employee
February 12, 2017

Hi,

Please share these logs with me at ksaini@adobe.com in case it bounces on fmerror. Also can you try with deleting FM appdata?

Thanks

Kunal

O
ohne_hosenAuthor
Inspiring
February 13, 2017

Sent. I did try deleting the appdata, but I still have problems.

I have discovered that if I open the EDD I'm having trouble with and update its references (I am working with DITA EDD modules), It seems to work. I don't want to risk scrolling down and having it crash again.

So maybe it's just that the references weren't updated before, but I would think FM should handle problems like this a bit more gracefully?

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices