Closed Bug 644084 Opened 13 years ago Closed 13 years ago

crash [@ nsAccessNodeWrap::get_attributesForNames(unsigned short, unsigned short**, short*, unsigned short**)]

Categories

(Core :: Disability Access APIs, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

VERIFIED FIXED
mozilla5
Tracking Status
blocking2.0 --- .x+

People

(Reporter: MarcoZ, Assigned: surkov)

Details

(Keywords: crash, Whiteboard: [A11Y Priority 1])

Crash Data

Attachments

(2 files)

This bug was filed from the Socorro interface and is 
report bp-fa75b724-d2f2-47d6-bd60-5746b2110323 .
============================================================= 
I found this while trying to reproduce reports that JAWS and Window-Eyes do not work with Firefox 4 under Windows XP. While JAWS virtual cursor simply doesn't work, running Window-Eyes with Firefox 4 produces this crash reliably.

This is isolated to Windows XP, does not happen on Windows 7.
Component: Disability Access → Disability Access APIs
Product: Firefox → Core
QA Contact: disability.access → accessibility-apis
Target Milestone: --- → mozilla2.0
Attached patch patchSplinter Review
regression from bug 541618 (http://hg.mozilla.org/releases/mozilla-2.0/diff/117fe7a234cc/accessible/src/msaa/nsAccessNodeWrap.cpp#l1.152)
Assignee: nobody → surkov.alexander
Status: NEW → ASSIGNED
Attachment #521134 - Flags: review?(marco.zehe)
blocking2.0: --- → ?
Comment on attachment 521134 [details] [diff] [review]
patch

r=me. This fixes the initial crash on startup, and a first page comes up in WE with the virtual buffer working. However, then activating a link to go to any other page causes another crash. Unfortunately, I can't debug this since my XP is not a good install really and debugging always means a freezing screen reader so i can't work the VStudio UI. So there seem to be other parts of the code that react badly on XP now somehow.
Attachment #521134 - Flags: review?(marco.zehe) → review+
Do we have a stack for the comment 2 case?
(In reply to comment #3)
> Do we have a stack for the comment 2 case?

it sounds crashreported is switched off on local builds (perhaps it doesn't make sense at all in this case), and Marco can use VS (per comment 2) to get it locally.
blocking2.0: ? → .x+
Whiteboard: [A11Y Priority 1]
Attached patch patch to landSplinter Review
Whiteboard: [A11Y Priority 1] → [A11Y Priority 1][fx4-rc-ridealong][has reviewed patch]
landed - http://hg.mozilla.org/mozilla-central/rev/8547ac6aefb7
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [A11Y Priority 1][fx4-rc-ridealong][has reviewed patch] → [A11Y Priority 1]
Target Milestone: mozilla2.0 → mozilla2.2
Verified fixed in ▪Build-Identifikator: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.2a1pre) Gecko/20110329 Firefox/4.2a1pre (but actually running on XP of course, not as shwon here on Windows 7)
Status: RESOLVED → VERIFIED
Crash Signature: [@ nsAccessNodeWrap::get_attributesForNames(unsigned short, unsigned short**, short*, unsigned short**)]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: