Flare 10.2 keeps hanging

[amarchant]

Flare 10.2 keeps hanging on me when I'm in the middle of editing a topic. This always happens when I'm actually typing something or using keyboard navigation like the arrow keys, never when I'm idling or working in another application. It suddenly freezes and won't respond to the pointer at all. I can't type, can't select text, can't change to a different topic, can't close Flare,... All the other applications I'm running work fine.

I have tried waiting for Flare to come back, but it never happens. I've waited about 10 minutes to no avail. I have to kill Flare in Task Manager and then restart it. Interestingly, Flare is always consuming CPU when I kill it (maybe 2 or 3 percent), so it seems to be doing something. There is often a CPU spike that appears in Task Manager about the time that Flare hangs.

This just started last week. I've been using 10.2 since it was released and it worked fine until a few days ago. It happens up to 10 times a day. Sometimes I've only typed about half a sentence before Flare hangs again. I've tired rebooting (soft and hard), uninstalling and reinstalling Flare, deleting Flare's Analyzer and Output folders, and stopping some of the services that I've got running. I haven't installed anything new or changed my system in any way, and I checked with my IT department and they haven't pushed anything to my computer.

Has anyone else had a similar problem? If so, what did you do to fix it?

[Lydia]

Since a few days I also experience problems with Flare hanging/ not responding. Killing it was the only option.
It happens when opening the Topics folder in the Content Explorer. The project I'm currently working on has many subfolders in there and the view is not updating.
I'll open a case with MadCap support about this.

[amarchant]

It sounds similar, Lydia, although for me it happens when I'm editing. I've also opened a Support ticket.

[amarchant]

Problem solved. Madcap Support sent me a list of things to try, but I think that it was repairing .NET that actually fixed the problem.

Here's an excerpt from the email I got from Support: "Please try performing a repair of all the instances of Microsoft .NET Framework on your machine by using the Microsoft tool below: http://www.microsoft.com/en-us/download ... x?id=30135".