Closed Bug 790094 Opened 12 years ago Closed 9 years ago

Firefox crashes/freezes with JAWS 13.0

Categories

(Core :: Disability Access APIs, defect)

15 Branch
x86
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: livdera, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, helpwanted)

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20100101 Firefox/15.0.1
Build ID: 20120905151427

Steps to reproduce:

Browsing certain webpages with lots of links / possibly using DOM/Ajax (unsure.)


Actual results:

Firefox either crashes outright or freezes and requires a force close through the Task Manager. This is usually preceded by JAWS 13.0 briefly freezing and the sound of my computer ramping up a bit (perhaps a memory spike?) When JAWs unfreezes a few seconds later, Firefox has either crashed or is frozen or JAWS reads things sluggishly until Firefox ultimately crashes/freezes. Upon restarting Firefox, browsing is normal for a little bit (5-10 minutes) before it crashes/freezes again.


Expected results:

Browser shouldn't crash/freeze inconjunction with JAWS 13.0.
Component: Untriaged → Disability Access
Crash Signature: Report ID Date Submitted  bp-3560cc0d-94e3-4eaa-abc6-d05182120910 09/09/2012 9:57 PM  bp-d7b9c3be-ef02-4891-b0e0-58a922120909 09/09/2012 5:33 PM  bp-ad3bec7e-c7f6-4080-b593-0ad262120909 09/09/2012 2:56 PM
Just a note that this problem did not happen with JAWS 9.0 - it only happened after I recently updated to JAWS 13.0. Something in the updated software is conflicting with Firefox.

I really love Firefox and I don't want to have to switch browsers - is there any fix for this?
Just a note that this problem did not happen with JAWS 9.0 - it only happened after I recently updated to JAWS 13.0. Something in the updated software is conflicting with Firefox.

I really love Firefox and I don't want to have to switch browsers - is there any fix for this?
unfortunately all 3 crash reports reports are with a corrupted stack.
I hope that some of the accessibility guys can help here
Crash Signature: Report ID Date Submitted  bp-3560cc0d-94e3-4eaa-abc6-d05182120910 09/09/2012 9:57 PM  bp-d7b9c3be-ef02-4891-b0e0-58a922120909 09/09/2012 5:33 PM  bp-ad3bec7e-c7f6-4080-b593-0ad262120909 09/09/2012 2:56 PM
Added a few more crash reports - hopefully one of them isn't corrupted. A lot of the crashes are really Firefox freezing and me having to force-close it. It's quite annoying.
Crash Signature: bp-e95dbe10-988b-4a0d-bad0-b73bf2120911 10/09/2012 9:55 PM  bp-63756000-1e5e-4aba-bd7b-a4e2d2120911 10/09/2012 8:27 PM  bp-4d197dac-28d1-4bf1-8c3d-71f5f2120911 10/09/2012 8:14 PM  bp-e48c804c-ffd6-40f9-9a9d-ebc6e2120910 10/09/2012 6:48 PM
(In reply to Kristen from comment #0)

> Steps to reproduce:
> 
> Browsing certain webpages with lots of links / possibly using DOM/Ajax
> (unsure.)

Kristen, if you can provide the urls of the sites you visited and be more descriptive-say which links you clicked etc on that page, it will be very useful for investigative purposes.
putting crash links in comment for linkification

bp-e95dbe10-988b-4a0d-bad0-b73bf2120911
10/09/2012
9:55 PM 
bp-63756000-1e5e-4aba-bd7b-a4e2d2120911
10/09/2012
8:27 PM 
bp-4d197dac-28d1-4bf1-8c3d-71f5f2120911
10/09/2012
8:14 PM 
bp-e48c804c-ffd6-40f9-9a9d-ebc6e2120910
10/09/2012
6:48 PM
All of these are empty/corrupted stacks, too. URLs to web pages where you see these crashes would indeed help I believe.
Severity: normal → critical
Crash Signature: bp-e95dbe10-988b-4a0d-bad0-b73bf2120911 10/09/2012 9:55 PM  bp-63756000-1e5e-4aba-bd7b-a4e2d2120911 10/09/2012 8:27 PM  bp-4d197dac-28d1-4bf1-8c3d-71f5f2120911 10/09/2012 8:14 PM  bp-e48c804c-ffd6-40f9-9a9d-ebc6e2120910 10/09/2012 6:48 PM
Keywords: crash
Unfortunately it seems to be pretty random when it happens - after 10-15 minutes of steady browsing (maybe a half hour if I'm lucky), Firefox will either outright crash (providing those empty/corrupted stacks) or will freeze outright and force me to forcibly close the program. This also will freeze JAWs for a little bit, as well.

I mean - this also happened on this Bugzilla site (which I found hilarious.)

Though the site where it happens most often is the one I do a lot of browsing on: http://www.furry-paws.com.
Taking care of the virtual dogs requires a lot of clicking links - about 4-5 per dog - and entering them in competitions takes several more clicks and loading of a long list/table of enter form buttons.

However, I used this fine with JAWs 9.0 + Firefox before - it's only JAWS 13.0 + Firefox, it seems. (I've seen other reports that indicate Firefox and JAWS started to not get along once JAWs hit 11.0 - that was when significant changes in the programming for JAWS changed from 9.0, I believe.)

Any help is appreciated.
Kristen I gues you don't have visual studio installed right?
Severity: critical → normal
David, would you mind grabbing one of  those crash dumps and seeing if msvc will do anything more useful with it?
Some more crash reports from tonight:
bp-6a9e8b2f-efe0-4274-b7e1-867e42120912
9/11/2012
9:30 PM 
bp-d8afa19b-f841-4304-bfa5-835572120912
9/11/2012
9:00 PM 
bp-9325f358-de16-4f14-8a2f-36e6a2120912
9/11/2012
8:42 PM 
bp-3f460a74-f1e4-4157-82eb-39f352120912
9/11/2012
8:33 PM 
bp-d0b20d75-590b-4132-9d90-09a4c2120911
9/11/2012
7:31 PM 
bp-aebd4353-11b7-49e7-819e-3f2e92120911
9/11/2012
7:19 PM 


I also noticed tonight that, when I had to do a forced closure by ending the process in the task manager, that eventually I'd end up with 2 Firefox.exe processes - 1 that I could close and the other one would give me an error when I tried to close/end it. Both had usages (I believe that would be what the number is) of over a million.

And, funnily enough, I do have Visual Studio. However, I just recently upgraded to Windows 7 from Vista and haven't had a chance to reinstall yet. (And yes - I had the exact same freezing/crashing problems with Firefox when using Vista, too.)

I'm not sure what function of JAWS Firefox is interfering with or conflicting with, though it's weird. It always slows JAWS down considerably in its reading of whatever webpage I am on before crashing/freezing.
I downloaded/installed the debugging tools, though they are unfortunately inaccessible to JAWS 13.0. I'll have to try it out this weekend when my sighted boyfriend can properly type the commands in, etc.

Any other suggestions in the meantime would be appreciated. I tried downgrading to a lower version of FF, though it was more sluggish in reacting with JAWS and I wasn't sure what was worse - frequent crashes or slow response time.
Tried to do the debugging thing, though seem to be stuck o the downloading of Firefox symbols - it gives an error that it can't verify the checksum on firefox.exe. And then when I try to open tehl ogfile, it says it can't be done.
Severity: normal → critical
Keywords: helpwanted
Component: Disability Access → Disability Access APIs
Product: Firefox → Core
Does this still happen?
Note: I emailed the reporter to see if we can confirm/reproduce or close this one.
Kristen, does this still happen with Firefox 19? I can try to get someone else to test it, too. 

It looks like you went through quite a lot of crashes and crash reports. Thanks for doing all that!
Flags: needinfo?(livdera)
It looks, also, like JAWS is to version 14 now.
Yes - this is still happening. I've had several more crashes. I find it happening quite a bit when I go to the Google News feed, though sporatically. I'm unsure what may be causing it, though it seems to happen even when I have Javascript blocked with NoScript or have no plugins enabled, as well. However, it seems to happen more often on Java or Flash-heavy sites.

And yes, it's to JAWS14 now, though JAWS 13 is still the version I (and probably a majority of people) are using. JAWS 14 is pretty much JAWS 13 with Windows 8 support.
Flags: needinfo?(livdera)
Status: UNCONFIRMED → NEW
Ever confirmed: true
I'm going to close this report because given the time delay it really isn't actionable. Kristen thanks for filing it, and if you get more crashes please file a new bug with a link to the crash report like you did in comment 11, along with any ideas about steps to reproduce the issue. Thanks!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.