Page 1 of 1
[Rumble 5.1.2] System Freezes when Character Editor is open
Posted: Fri Apr 22, 2011 3:33 pm
by kneverwinterknight
Hi Rumble,
I don't know if this is an issue with the FW or my machine, but when I open the Character Editor for a character which is illuminated by the initiative marker, the system freezes up.
Re: [Rumble 5.1.2] System Freezes when Character Editor is o
Posted: Wed Apr 27, 2011 5:14 pm
by Rumble
kneverwinterknight wrote:Hi Rumble,
I don't know if this is an issue with the FW or my machine, but when I open the Character Editor for a character which is illuminated by the initiative marker, the system freezes up.
Is that reproducible every time? I have seen occasional system freezes with the character editor open, but I had never been able to nail it down to a particular set of circumstances. If so, that would be very helpful!
Re: [Rumble 5.1.2] System Freezes when Character Editor is o
Posted: Thu May 05, 2011 4:42 pm
by kneverwinterknight
Hi,
It doesn't reproduce every time. I've encountered it 3 times since my original post. If it happens again, I will let you know.
Re: [Rumble 5.1.2] System Freezes when Character Editor is o
Posted: Tue Sep 27, 2011 3:45 am
by Colmarr
For what it's worth, I encountered this problem for the first time a fortnight ago, and it occurred 3 times in the same session.
I didn't think to note whether the token I was editing was the one that had initiative...
Re: [Rumble 5.1.2] System Freezes when Character Editor is o
Posted: Tue Sep 27, 2011 9:55 am
by Rumble
I don't know what the initiative link might be (or if there is one), but I know that another user discovered a race condition in MapTool that caused system lockups with frames and dialogs. It's discussed over in Bug Reports, and Azhrei says that the patch to the bug was applied and is in testing.
Feedback on the patch is positive - one tester who was experiencing regular lockups with frame-heavy frameworks isn't seeing that problem anymore. So, if it's that lockup issue, there's nothing that can be done except waiting; it's internal to MapTool, not the framework.
If there's another issue in the framework itself, I still would recommend a wait-and-see approach because it could be clouded by the frame-lockup bug.