Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

It happens on both, actually. The last 6 months or so I've been working on my local drive because the network drive server is now remote instead of on-site and the lag was really annoying. At least it wasn't bouncing. On Thu, May 18, 2017 at 9:54 AM, Alan Houser wrote:

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

Just to mention a possibility ... FrameMaker is rather intolerant of network latency. If you are saving to any sort of networked drive (even a Dropbox folder), try saving to a local drive. I've had more than one client drastically reduce random FrameMaker crashes by moving from network to

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

2:02 PM > To: An email list for people using Adobe FrameMaker software. > Subject: Re: [Framers] Crash with Internal Errors: 13054, 21985197, > 21967009, 21686210 > > Bernard: All of the graphics are SVGs, created by Visio 2013. Frame has the > same habit of adding colors to t

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

[mailto:framers-bounces+acraig=bkultrasound@lists.frameusers.com] On Behalf Of Lin Sims Sent: Wednesday, May 17, 2017 2:02 PM To: An email list for people using Adobe FrameMaker software. Subject: Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210 Bernard: All

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

Rather than deleting the figures you could just substitute placeholders long enough to determine whether those are the problem. You can't refer to the SVGs in some other program? I had various problems with Visio graphics which all went away when I started placing them as EMFs. On Wed, May 17,

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

Bernard: All of the graphics are SVGs, created by Visio 2013. Frame has the same habit of adding colors to the catalog with them, too. Not sure if the rename (of only Black!) has any bearing, but it struck me as odd so I mentioned it. Robert: Not sure if removing the graphics would help, since

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

What if you temporarily remove the 18 embedded figures? On Wed, May 17, 2017 at 11:51 AM, Lin Sims wrote: > Anyone know what these errors refer to? I have a file that frequently > crashes Frame, and this was the latest series of internal errors it gave me. > > I did do a MIF

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

bulk Shift+Delete them on my computer. Bernard -Original Message- From: Framers [mailto:framers-bounces+bernard=publishingsmarter@lists.frameusers.com] On Behalf Of Lin Sims Sent: Wednesday, May 17, 2017 2:52 PM To: Frame Users Subject: [Framers] Crash with Internal Errors: 13054

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

As far back as I can remember, the lore was that those error numbers only had meaning to whomever created the message. There were no specific fixes. My old troubleshooting mind remembers when tweaking some resource settings in early Windows releases sometimes helped fix application problems. I

Re: [Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

Other fun stats: I have 104 crash log files since last July I had 14 crashes in 1 day this February So far today, I've had 3 crashes Seriously, this is getting OLD. And my nearby coworkers are gaining new "respect" for my ability to curse and swear. On Wed, May 17, 2017 at 2:51 PM, Lin Sims

[Framers] Crash with Internal Errors: 13054, 21985197, 21967009, 21686210

Anyone know what these errors refer to? I have a file that frequently crashes Frame, and this was the latest series of internal errors it gave me. I did do a MIF wash and noticed one odd thing: Frame has renamed the color Black to fm_gen_## when I save to the MIF file. If I edit those