Overflow error in Flare v6.1

This forum is for all Flare issues not related to any of the other categories.
Post Reply
Craig.Prichard
Propeller Head
Posts: 62
Joined: Sat Dec 10, 2005 8:06 pm
Location: Calgary, AB Canada

Overflow error in Flare v6.1

Post by Craig.Prichard »

Happening more and more frequently in my project, while editing a topic (usually pasting content) Flare will generate an Unhandled exception overflow error. I can continue editing and save changes without corruption (I hope) but the UI will place a red x-ed box between the topic content and the "Show spans" area of the window. A peak inside the source code shows a MadCap:lastwidth="4.294967E+09" or some similarly outrageous value. Why? I delete MadCap: lastBlockDepth, lastHeight, and lastWidth, in the source code, save the file, then open it again in Flare's XML editor. The red x-ed box will be gone but I will crash Flare again if I try make the same edit change. I have compared a clean copy of the file with a crashed copied where I saved the crashed copy even though Flare didn't identify the file as needing to be saved. The comparison shows that MadCap: lastBlockDepth, lastHeight, and lastWidth have been added and MadCap:lastwidth has a ridiculous value again. Flare will generate my targets successfully with either version.

Any suggestions?
Andrew
Propellus Maximus
Posts: 1237
Joined: Fri Feb 10, 2006 5:37 am

Re: Overflow error in Flare v6.1

Post by Andrew »

Two suggestions:

1) Reset your window layout. (Window > Layouts > Reset Window Layout).

2) If that doesn't work, contact MadCap support.
Flare v6.1 | Capture 4.0.0
Craig.Prichard
Propeller Head
Posts: 62
Joined: Sat Dec 10, 2005 8:06 pm
Location: Calgary, AB Canada

Re: Overflow error in Flare v6.1

Post by Craig.Prichard »

For the sake of thoroughness I will reset Layouts. However, this is happening since my harddrive was replaced last weekend and I installed Flare v6.1 fresh on Monday. Since the install I have not many Flare UI changes, including creating or saving any Layouts.

But I think you are on the right track. The crashes coincide with the XML editor window struggling to refresh and properly display table rows containing two (2) columns: text and a thumbnail PNG image. Turning on or off the various display options, e.g. conditions, table rows and columns, has no impact on the type or frequency of crashes.

At the least I would think that the Flare code would have enough error handling to prohibit extremely high width or height values from being set in the meta data (and elsewhere as necessary).
rob hollinger
Propellus Maximus
Posts: 661
Joined: Mon Mar 17, 2008 8:40 am

Re: Overflow error in Flare v6.1

Post by rob hollinger »

Based on what Im reading, I would assume the layout your editing in is Layout(print).
There is a table in the topic and I also assume this topic is several pages long.
When you paste content into the topic, it kicks off the pagination engine which re-applies the page breaks based on settings from the style sheet (page break options). If there are a lot of page break options set (lists, cells, rows, headings, etc) it can get complicated real fast.
If your topics are several pages long, I would suggest editing them in Layout(web) which does not use the pagination engine to avoid the crash. After the edits are done, you should be able to switch back to layout(print).

You should log this with support. Please provide the topic, style sheet, and page layout with the steps and information needed to replicate the issue.
https://www.madcapsoftware.com/bugs/submit.aspx
Rob Hollinger
MadCap Software
RTFMer
Jr. Propeller Head
Posts: 1
Joined: Tue Jun 23, 2015 8:11 am

Re: Overflow error in Flare v6.1

Post by RTFMer »

Andrew wrote:Two suggestions:

1) Reset your window layout. (Window > Layouts > Reset Window Layout).

2) If that doesn't work, contact MadCap support.
I realise it's been five years, but just wanted to come upvote this as I just got myself in a snarl and this fixed my issue! Thank you, Andrew! A timeless solution! (I'm on Flare v11.)

Oops, no, I spoke too soon. <sigh> Tech support, here I come. :-/
Post Reply