Closed Bug 970089 Opened 11 years ago Closed 11 years ago

long (infinite?) loop in a11y:FocusManager::ProcessFocusEvent

Categories

(Core :: Disability Access APIs, defect)

x86_64
Windows 8
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 970005

People

(Reporter: vlad, Unassigned)

References

(Blocks 1 open bug)

Details

I've frequently hit infinite loops in Firefox, with the debugger placing me in xul.dll!mozilla::dom::Element::GetAttr(int aNameSpaceID, nsIAtom * aName, nsAString_internal & aResult) Line 1946 C++ xul.dll!mozilla::a11y::RelatedAccIterator::RelatedAccIterator(mozilla::a11y::DocAccessible * aDocument, nsIContent * aDependentContent, nsIAtom * aRelAttr) Line 88 C++ xul.dll!mozilla::a11y::FocusManager::ProcessFocusEvent(mozilla::a11y::AccEvent * aEvent) Line 314 C++ xul.dll!mozilla::a11y::EventQueue::ProcessEventQueue() Line 478 C++ xul.dll!mozilla::a11y::NotificationController::WillRefresh(mozilla::TimeStamp aTime) Line 273 C++ xul.dll!nsRefreshDriver::Tick(__int64 aNowEpoch, mozilla::TimeStamp aNowTime) Line 1079 C++ xul.dll!mozilla::RefreshDriverTimer::Tick() Line 160 C++ Trying to step out of the FocusManager::ProcessFocusEvent call results in a loop where breaking in is somewhere inside deeper code, or in PLDHash code. I'm on Windows 8 (not 8.1), on a desktop, but with various tablet PC things enabled because I have a Leap Motion controller that can make use of the on-screen keyboard. I had accessibility.win32.force_disabled set to true, but accessibility.force_disabled was 0. I just set it to 1, but this is a bad experience -- remnants of bug 538530.
Is this similar to bug 970005?
(In reply to Marco Zehe (:MarcoZ) from comment #1) > Is this similar to bug 970005? yes, also caused by bug 933322
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.