Processing lag in 2017 r2 causing big trouble

[jack16]

Since our upgrade to Flare 2017 r2, keystrokes, selection of images, right-click menus, etc., etc., lag terribly. I tried to ignore it at first, but over time, it's become a big productivity kill. I submitted a bug to Flare, was told it's probably due to the Windows Creators update and there's no timeline for when the issue is going to be fixed. In the meantime, has anyone gerryrigged a solution? How're you coping with the lag? It's got me pretty depressed. I always believed Flare was for writers.

[cdschroeder]

I have the same issue after upgrading to a new computer. Talked to MadCap yesterday and gained a little more clarity on the issue. The problem is caused by a conflict between Flare and .NET Framework 4.7. Unfortunately, .NET Framework 4.7 is installed with the Creator's update, and after installing the Creator's update, you cannot downgrade to an earlier version of .NET Framework (thank you, Microsoft). Our IT department confirmed this as well, and said there is no workaround (aside from using another computer).

Anyway, MadCap assured me that it is a known issue and they are working on it. So I am optimistic for a fix, because they can't just stop supporting customers with the Creator's update. But in the meantime, I would advise those who have not yet installed the Creator's update to avoid it for now.

[jack16]

Really appreciate the informative response. Never hurts to be reminded that misery has company. (Yes, it could be worse, but I use Flare 80-90% of each day, so its performance is tied to my own.)

[cdschroeder]

Really appreciate the informative response. Never hurts to be reminded that misery has company. (Yes, it could be worse, but I use Flare 80-90% of each day, so its performance is tied to my own.)

Same here. I feel your pain.

Although, there is something we can do. As I was reminded by my boss yesterday, the fastest way to get a bug fixed is to keep calling in and checking on its status. Bonus points if multiple people/companies do it. So, we might as well keep "bugging" them till they fix it.

For reference, the bug number is #131358.

[Paulie]

The latter portion of the thread at the following URL seems to be describing something very similar to the issue that is affecting Flare. With any luck, hopefully a fix will be out shortly.

https://github.com/Microsoft/dotnet/issues/393

[owenf]

Me too. Flare 11 used to run lovely, even when i got a new Windows 10 laptop (some massive issues with screen res aside).

Now it has real trouble, to the point where i wait for 1-2 seconds for a keystroke to complete. sometimes it gets temporarily better, more often i need to kill Flare.exe.
So, using the info on this thread, i discovered that i am on .NET framework 4.6.1. So I went to see if something changed in there, recently, and it looks to me like the WPF might be the culprit - my WPF (windows presentation format) files / libraries are newer than the rest of the framework.

Flare has always had issues with display, multiple monitors etc, and i reckon this intersection is killing it. I do hope MadCap consider backporting any patches they make to Flare 11.

[Roland Weigelt]

The latter portion of the thread at the following URL seems to be describing something very similar to the issue that is affecting Flare. With any luck, hopefully a fix will be out shortly.

https://github.com/Microsoft/dotnet/issues/393

The fix mentioned in that thread by user "NikolaMilosavljevic" (MS employee) is now in the "2017-07 Cumulative Update for Windows 10 Version 1703 [...] (KB4032188)".
The update didn't show up in Windows Update on my computer (yet), but it is available on the Microsoft Update Catalog http://www.catalog.update.microsoft.com ... =KB4032188.

I tried the x64 version and - drum roll - my Flare 2017 r2 works beautifully!

I had contacted MadCap recently, describing the keyboard lag in detail (repro steps, trying to figure out whether there are patterns, etc.). I now can do all the things that triggered the lag and it is gone (within a reasonable level of expectations).

DISCLAIMER: If the update breaks anything on your computer, don't blame me, etc.

[Rona Kwestel]

Am I the only one who finds it maddening that when you report this issue to Flare Support, they act as if this is only happening to you, and send you the same old tired instructions about "repairing" your .NET framework (which is such a strange process that it's impossible to tell what, if anything, it's doing), clearing the Flare registry, and deleting that Catapult folder, only to lose all your settings and not actually fix anything at all?

Unfortunately, I downloaded and tried installing the Microsoft Update Catalog (http://www.catalog.update.microsoft.com ... =KB4032188) fix suggested above, and it said "The update is not applicable to your computer." : - (

[B4ss]

The latter portion of the thread at the following URL seems to be describing something very similar to the issue that is affecting Flare. With any luck, hopefully a fix will be out shortly.

https://github.com/Microsoft/dotnet/issues/393

The fix mentioned in that thread by user "NikolaMilosavljevic" (MS employee) is now in the "2017-07 Cumulative Update for Windows 10 Version 1703 [...] (KB4032188)".
The update didn't show up in Windows Update on my computer (yet), but it is available on the Microsoft Update Catalog http://www.catalog.update.microsoft.com ... =KB4032188.

I tried the x64 version and - drum roll - my Flare 2017 r2 works beautifully!

I had contacted MadCap recently, describing the keyboard lag in detail (repro steps, trying to figure out whether there are patterns, etc.). I now can do all the things that triggered the lag and it is gone (within a reasonable level of expectations).

DISCLAIMER: If the update breaks anything on your computer, don't blame me, etc.

Downloaded and installed the latest update to Windows 10 referenced by KB4032188, and it seems to solve this issue. More information:
https://support.microsoft.com/en-nz/hel ... -kb4032188
Still testing that the lag and performance issues are solved, but all looks well so far.

[jaynalocke]

Another solution, for those who have not upgraded to Windows 10, is to upgrade your .NET Framework to version 4.7. This includes a patch that resolves the performance problems in Flare 17 R2. See https://www.microsoft.com/net/download/framework.

[Nita Beck]

About time you showed up, Jayna!

[jaynalocke]

Hi Nita! Yes, I need to start carrying my weight.

[eclecticbanana]

Windows 10 update KB4038782 (https://support.microsoft.com/en-us/hel ... -kb4038782) appears to have fixed processing lag on my end. Installed via Windows Update.