Hi Rebecca,
A file may crash either because it has problems in its metadata (pieces of
information about some variables, conditions, tags brought to the document by
Copy/Paste) or it contains too many (unused)
variables/conditions/paragraph/table and character tags. So, I would suggest to
run a script (Framescript/Extendscript), which deletes the unused
variables/conditions/tags (of course, back up the files first). This may help
to get rid of the junk that sneaked into those documents.
HTH,
Roman
________________________________
From: rebecca officer <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Thursday, November 10, 2011 12:49 AM
Subject: Re: Framemaker 10 crashes when changing conditional text display
setting
Hi Roman
That's interesting. I did manually save the file as MIF.
Did you try/find anything else? Anything that your sick files had in common?
We're speculating it's FM's pagination engine getting upset with CT causing
repeated major changes to pagination. But that's pure speculation!
Cheers
Rebecca>>> On 10/11/11 at 01:30, Roman Banks <[email protected]> wrote:
Hi Rebecca,
I had a similar problem 2-3 times with specific FM files. Usually, manually
saving the files as MIF and then manually saving them back as FM10 solved the
problem.
HTH,
Roman
________________________________
From: rebecca officer <[email protected]>
To: [email protected]
Sent: Wednesday, November 9, 2011 8:24 AM
Subject: Framemaker 10 crashes when changing conditional text display setting
Hi everyone
We're getting Framemaker 10 crashes when changing conditional text display
settings on some files (3 so far out of several hundred). It crashes, for
example, when we toggle between build expressions and/or Show As Per Condition
settings. Depending on file and display settings, it crashes after anything
between 1 and 40ish display actions. 40 we could live with; 1 or 2 makes the
files unusable.
The error message is "Internal error 10014, 5988022, 5988444, 4795055".
Sometimes we have to forcefully close FM after this. Other times, FM closes
itself and we get another dialog box:
"The instruction at "0x033e76e0" referenced memory at "0x0d9af94b". The memory
could not be "read"."
Or sometimes, 'the memory could not be "written"'. And once, it was "the
exception Privileged instruction. (0xc0000096) occurred in the application at
location 0x0c76e57a."
The hex values vary from PC to PC but the actions to cause each crash don't.
The files have multi-page tables with conditional text in the tables. They were
created in Frame 7.0 and upgraded straight to 10.0.0. We're using conditional
text with 11 conditions and 8 boolean expressions.
I've trawled the forum and frameusers list, and tried:
* 5 different machines - they all see the issue.
* washing through MIF - the MIF files crash FM too.
* working locally instead of across the network - no difference.
* showing all conditions and then looking in the Mif files for any text in a
flow called "Hidden". There wasn't any.
* saving after every change of conditional text display setting. This sometimes
works but it's a pain!
* removing all the paragraph overrides in the file. This worked for 1 out of 3
files.
* removing the tables and/or removing conditional text from them. This worked
for 2 out of 3 files, and improved the 3rd, but I don't think it's a feasible
fix.
We're all running FM 10.0.1.402 on Win XP Pro SP3, 32 bit machines. The amount
of RAM varies, but some PCs have 4 Gig. We've all installed the MS hotfix for
the text dropout issue. Files are unstructured.
Has anyone else seen anything like this? Any ideas of anything else we can try?
Any ideas of a cause??
Many thanks,Rebecca
PS X-posting this to the Adobe Frame forum. Apologies to people who're on
both.NOTICE: This message contains privileged and confidentialinformation
intended only for the use of the addresseenamed above. If you are not the
intended recipient ofthis message you are hereby notified that you must
notdisseminate, copy or take any action in reliance on it.If you have received
this message in error pleasenotify Allied Telesis Labs Ltd immediately.Any
views expressed in this message are those of theindividual sender, except where
the sender has theauthority to issue and specifically states them tobe the
views of Allied Telesis Labs.
_______________________________________________You are currently subscribed to
framers as [email protected] list messages to
[email protected] unsubscribe send a blank email
[email protected] visit
http://lists.frameusers.com/mailman/options/framers/banks_roman%40yahoo.comSend
administrative questions to [email protected].
Visithttp://www.frameusers.com/ for more resources and info. NOTICE: This
message contains privileged and
confidentialinformation intended only for the use of the addresseenamed
above. If you are not the intended recipient ofthis message you are hereby
notified that you must notdisseminate, copy or take any action in reliance
on it.If you have received this message in error pleasenotify Allied
Telesis Labs Ltd immediately.Any views expressed in this message are
those of theindividual sender, except where the sender has theauthority
to issue and specifically states them tobe the views of Allied Telesis
Labs. _______________________________________________You are currently
subscribed to framers as [email protected] list messages to
[email protected] unsubscribe send a blank email
[email protected] visit
http://lists.frameusers.com/mailman/options/framers/banks_roman%40yahoo.comSend
administrative questions to [email protected].
Visithttp://www.frameusers.com/ for more resources and info.
_______________________________________________
You are currently subscribed to framers as [email protected].
Send list messages to [email protected].
To unsubscribe send a blank email to
[email protected]
or visit
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com
Send administrative questions to [email protected]. Visit
http://www.frameusers.com/ for more resources and info.
