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?

I wish I knew. This is a crippling problem that nullifies an essential feature of the released product. It shouldn't take a service contract for Adobe to fix major flaws like this.

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.

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.

I am not using Track Changes but disabled it anyway across the book. FM still crashes. I changed from Adobe PDF as the printer in Printer Setup to the default network printer here.  FM still crashes.

@Jeff_Coatsworth,

Did you get a better suggestion or solution from Adobe support?

Not saying you need to reveal it here. After all, "you" paid for the call.

I'm trying to figure out if this issue is worth my firm signing up for support.

All I know is I didn't need it on FM8.

Best,

@Jeff_Coatsworth:  Doh!  Thanks.

@TekCon:  Any contact with support on this?  Wazzup?

Plenty of folk have reported the issue. No sign of a solution.

BTW: TekCom = Tekscribe

The first name is from personal FM license (old profile created from home base), the second is from employer/company FM license (created recently via the office). Sorry for the confusion and redundancy.

I do not have another similar machine readily available for FM11 test. No time either. I need to get work done (while carefully avoiding provoking another FM10 crash), aside from posting to this Forum and chasing Adobe Engineering.

The particular book/project that crashes was run (i.e. Update Book) successfully on a WinVista 32-bit machine running FM10+update. I may have mentioned this in the other discussion. So, my favorite theory presently is ... the crashing is tied to hardware (i.e. laptops), software (installed on the laptop), or O/S (i.e. FM10 does not function well in 32-bit mode on a 64-bit machine).

So, cross-references and/or multiple conditionals may be the trigger, but hardware, software, and/or O/S may be the fuel feeding the crash-fire.

I may have mentioned but will repeat: the chronic crashing is happening on two different but indentical HP laptops.

Suzanne,

The HP laptops do not have any other FM version installed. Only FM10. The home machine (running WinVista 32-bit) mentioned above does have FM8 installed as well yet I was able to Update Book successfully for the same heavily conditioned project. So, the prescence of another FM is not relevant in my case. It may be an issue in other circumstances; however, optimistically I assume Adobe would suggest users uninstall old versions or the new version would do that automatically upon installation if conflicts were anticipated by their engineers/testers.

You may have achieved something accidently either by virtue of the FM8 removal or the FM10 uninstall/re-install. From experience, I think there are a variety of reasons FM misbehaves and gives up the ghost. IMO, it would be better for users to have some idea what is giving FM grief, instead of useless, cryptic error message coughed up by the software. Adobe: Are you listening?

I am sticking with the theory outlined above for chronic crashes here. For sure, conditional content has something to do with it but only in certain circumstances (hardware, software, services, conflicts, memory allocation, alignment of the planets, etc.).

In the response I got from an Adobe engineer, they allegedly did test FM10 versus Win7 and 64-bit mode. According to Adobe, Win7 64-bit is a supported platform. However, I am not convinced they tested on a variety of machines (e.g. Lenovo or HP laptops).

All the same, it must be a relief that your situation is resolved. I wish mine was...

Mike

Win7 Enterprise 64-bit (Service Pack 1). I'll mention your suggestion to IT. I will not experiment further without their consent. In the meantime, I still await a response from an Adobe engineering team.

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