Participating Frequently

Question

Why is FM10 crashing when I change conditional text settings?

Forum|Forum|14 years ago
January 20, 2012
8 replies
17185 views

When I go from "show certain conditions" to "show all" in some, but not all, files in a book, FM 10 crashes.

I've tried saving as MIF, then reopening, but it still happens eventually.

Sometimes it happens with the first file I open, sometimes not until after several files have been opened and

had their conditions changed, so it doesn't seem like a memory leak.

This topic has been closed for replies.

A

Anonymous

"Progress" is right

Does anyone know if FM11 has this same issue with conditional text? I was going to keep with FM10 since the new "features" in FM11 really won't help me in any way, so I thought I'd save the company a few bucks and continue working in FM10. But if FM11 doesn't have this issue, then it might be worth it to go through the trouble of upgrading since I would have to reinstall FM10 anyway to see if that solves the problem...

Matt-Tech Comm Tools

Community Expert

I've been using FM11 for most of 2012 (I wrote the FM 11 Reviewer's Guide) and haven't had any problems with conditional text crashing.

In fact I'm working right now on a series of conditional text manuals (4 conditions, a few thousand pages)

But then again, I started working on these when they were in FM9, converted them to FM10, and now they're in FM11. I don't recall crashing at all while switching conditions. (That's not to say I haven't crashed at all...just usually when things time while waiting for unavailable resources)

-Matt

-Matt SullivanFrameMaker Course Creator, Author, Trainer, Consultant

A

Anonymous

Thanks for the feedback about FM11, Matt. I may ask IT to download the trial to a different system so I can do some testing with my files before making the purchase and uninstalling FM10.

We'll see how it goes...

Smitty

A

Anonymous

I get to join this thread now since FM10 has crashed on me for changing conditions...yay (?)

I have a book file with a Front file and Body file for a grand total of 10 pages (with all conditions showing - not a large doc by any means). I only have 7 conditions (which is not a lot considering at one company I had over 50 in one book and FM8 handled that just fine) and I have triple checked to make sure all the conditions are the same for each of the files in the book, which I thought could have been the problem - but no.

I am running Windows 7 on a 32-bit HP desktop, not laptop. This machine did not have a legacy version of FrameMaker installed on it - only FM10 when I received the PC (I am not working with TCS). I do have Photoshop, InDesign, and Illustrator installed along with Distiller X and Acrobat X.

I am amazed that with how many of us are having issues changing conditions that there is no patch! Everyone seems to have different system configurations and programs, but the problem is common to all. This makes me think that the issue lies somewhere deep within the code and has nothing to do with our system configurations or software that we are running...just my two cents.

Smitty

Tekscribe

Participating Frequently

I am still waiting for a response from Adobe engineering (entire book/files sent 10 days ago). I get the chronic crashing changing conditions across a large book with many, many conditions. FM also crashes in Update Book with All Cross Reference selected.

The one thing you mention that we have in common is Acrobat X. Apart from laptop peculiarities and Win7 64-bit suspicions, Acrobat X was one of my other theories as to the cause. I was not having problems before approximately the time we upgraded from Acrobat 9. However, other software changes took place during that time and I cannot be sure which one might be the culprit.

My colleague with the same machine and same software is also experiencing crashing. It happens mostly with one particular book every time, but randomly with other large, complicated books. Smitty, you may be right that there is a gremlin in the bowels of FM code.

The local IT expert here feels it has nothing to do with Win7 or 64-bit mode. His prime suspect is conflicting software (Acrobat X or Symantec Endpoint). Gremlins could be anywhere

Arnis Gubins

Inspiring

Thanks to Chetan for the response. Our local desktop support/IT person removed SEP. I updated the book exhibiting the consistent chronic crash issue - desired conditions set to Show and All Cross-References option selected. Result: same old crash. It is not SEP causing the problem.

Adobe engineering says it's not Acrobat X (their test machines all had Acrobat X). Local IT person says it's not O/S-related (or 64-bit), or a hardware issue (i.e. the HP Mobile Workstation). Therefore ... <drumroll> methinks FM has an ellusive BUG!

Adobe engineering has been silent - after I provided massive source files - and since online meeting with them, supplying more crash logs and source files. One can only speculate why the sparse response. Meanwhile, this user is stuck with a huge doc legacy based in FM, requiring workarounds to avoid regular crashes. It would be nice if Adobe corporate would pay attention. Perhaps FrameMaker is a back-burner product, not worthy of extensive investment.

Michael,

One thing that you mentioned was using OLE and lots of linked images. This has always been a bit of a sore point in FM that (depending upon the installation) has caused FM to misbehave. I wonder if that is exasperating the issue in your case?

A

Anonymous

I'm having the same problem. Adobe support said to do the MIF wash, which seemed to work, but the problem returned. I'm wondering if it's caused by combining conditions. I have a release condition (3 or 4) and an audience condition (external or internal).

S

ShannonMooneyMcKesson

New Participant

I have been plagued by the same internal error in Frame 10.

However, I did not receive an error when:

I opened the book, opened the chapter in my book, went to Special > Conditional Text and then either selected or deselected the "Show Condition Indicator" feature.

In my case, the error seems to be limited to trying to show/hide condition indicators from within the Show/Hide Conditional Text window.

S

scatonAuthor

Participating Frequently

All,

My original issue was resolved by removing FrameMaker 8 from my machine. I have not had a crash since then.

T

TekCom

Participating Frequently

I am getting this issue too. I click Show/Hide Conditional Text for multiple files in any book and Internal Error 10024, 9332515, 9332572, 7278063 displays just before FM crashes. I do not see a solution in the forum. I have tried MIF wash, rebuilding books, etc. This was not happening in the same books about 10 days ago; only things that have changed on the local machine are Adobe Flash, VPN client, and Mozilla Firefox updates.

Running the latest FM10 build on Win7 64-bit.

F

Frank_Stelter

New Participant

Another solution that works for us is to select the entire main text flow of the file, copy it to a blank frame file, and then save the temporary file. In the temporary file, you should be able to toggle your conditions on and off without an issue. If that works, delete the main text flow in the original file, save it in that state, and then copy the contents of the temporary file back in. Everything should be happy at this point.

R

rsaun781

New Participant

I've had this problem since release, and it is frustrating to no end. I've lost count of the number of hours of productivity lost due to this bug.

Can we have an Adobe rep inform us what the status of this bug is in terms of fixes? Can we expect a patch in the near future?

S

scatonAuthor

Participating Frequently

Do you know how to get Adobe to pay attention to this issue?

I don't have a maintenance contract ...

Suzanne

F

Frank_Stelter

New Participant

This happens to us as well, and has been persistent since Frame 9. One thing to try (if you're desperate, and we sure have been), is to break the problem file into smaller pieces to isolate the problem. For example, save the first half of the chapter as one file, and the second half as another -- repeat until you isolate or resolve. It seems to have something to do with conditionalized cross references, but we've never been able to fully resolve it.