Cristian Comorasu, QA [:ccomorasu], Releae Desktop QA - Please contact mboldan@mozilla.com Reporter
	Description • 7 years ago

[Affected versions]:
 Fx 57.0a1 (20170822171841)

[Affected platforms]:
 Windows 10 x64
 Windows 7 x64

[Steps to reproduce]:
 1. Open Firefox with a clean profile.
 2. Go to about:home .
 3. Open NVDA and hover over the page.

[Expected result]:
 The software works accordingly.

[Actual result]:
 The browser crashes.

[Regression range]:
 I return with the regression range as soon as possible.

[Notes]:
 Could not reproduce this issue on Windows 8x1 x32 .
 Crash reports:
  https://crash-stats.mozilla.com/report/index/f933f7f2-3330-4fab-8c64-3c6f20170823
  https://crash-stats.mozilla.com/report/index/ad0794c1-814e-4da6-8df2-2a8e90170823

	:Gijs (he/him)
	Comment 2 • 7 years ago

Why is this filed in reader mode?

	Cristian Comorasu, QA [:ccomorasu], Releae Desktop QA - Please contact mboldan@mozilla.com Reporter
	Comment 3 • 7 years ago

It is from my mistake, sorry. I will change it accordingly.

	Marco Zehe (:MarcoZ)
	Comment 4 • 7 years ago

Cristian, do you also get this crash if you start NVDA *before* you start Firefox? The two crash reports have different signatures. A blind user normally starts NVDA before Firefox. And I cannnot reproduce these crashes.

	Cristian Comorasu, QA [:ccomorasu], Releae Desktop QA - Please contact mboldan@mozilla.com Reporter
	Comment 5 • 7 years ago

Yes, as it opens the first page is the tab crash page and the browser does not respond.

	Xidorn Quan [:xidorn] UTC+11
	Comment 6 • 7 years ago

(In reply to Marco Zehe (:MarcoZ) from comment #4)
> The two crash reports have different signatures.

That doesn't really matter. Both reports are stack overflow having the same set of functions involving.

Could you try if it happens with non-stylo? As far as I know, we have one bug (bug 1390409) for a11y support on stylo. That may be related to this.

	Marco Zehe (:MarcoZ)
	Comment 7 • 7 years ago

Still get no crash.

	Cristian Comorasu, QA [:ccomorasu], Releae Desktop QA - Please contact mboldan@mozilla.com Reporter
	Comment 8 • 7 years ago

I can still reproduce it, here is a screen cast: http://imgur.com/a/hKTfL
And here is the crash report:
https://crash-stats.mozilla.com/report/index/ca448664-1d37-48a7-9f43-3b8c00170829

	Cristian Comorasu, QA [:ccomorasu], Releae Desktop QA - Please contact mboldan@mozilla.com Reporter
	Comment 9 • 7 years ago

I encountered tab crashes with Windows Narrator as well.

	David Bolter [:davidb] (NeedInfo me for attention)
	Comment 10 • 7 years ago

NI Aaron for awareness and in case he has any immediate thoughts.

	(No longer employed by Mozilla) Aaron Klotz
	Comment 11 • 7 years ago

Might be a dup of bug 1379951. Cristian, are you running Firefox off of a network drive by any chance?

	Cristian Comorasu, QA [:ccomorasu], Releae Desktop QA - Please contact mboldan@mozilla.com Reporter
	Comment 12 • 7 years ago

The behavior is very similar, however I am not running Firefox off a network drive. Also no prerequisites are required, it happens on a fresh profile.

	Marco Zehe (:MarcoZ)
	Comment 13 • 7 years ago

(In reply to Cristian Comorasu [:CristiComo] from comment #12)
> The behavior is very similar, however I am not running Firefox off a network
> drive. Also no prerequisites are required, it happens on a fresh profile.

As in "Fresh profile", "Notification about turning off accessibility appears then disappears", but browser isn't restarted? As was described in bug 1398054?

Can you still reproduce the issue if you allow the browser to restart once after creating the new profile?

	Cristian Comorasu, QA [:ccomorasu], Releae Desktop QA - Please contact mboldan@mozilla.com Reporter
	Comment 14 • 7 years ago

I re-tested with two machines with identical specifications, same build Fx 57.0a1 (20170912100139) same OS (Windows 10 x64) and the same version of NVDA(2017.3).
At the machine I could reproduce the crash I noticed in about:support under the "Important Modified Preferences" area, an extra pref code named "ui.osk.debug.keyboardDisplayReason" with the value "IKPOS: Touch screen not found.".

	David Bolter [:davidb] (NeedInfo me for attention)
	Comment 15 • 7 years ago

This might be a case of two consumers of accessibility API, which may cause unknown issues? I'm not familiar with the OSK debug info...

	:Gijs (he/him)
	Comment 16 • 7 years ago

(In reply to Cristian Comorasu [:CristiComo] from comment #14)
> I re-tested with two machines with identical specifications, same build Fx
> 57.0a1 (20170912100139) same OS (Windows 10 x64) and the same version of
> NVDA(2017.3).
> At the machine I could reproduce the crash I noticed in about:support under
> the "Important Modified Preferences" area, an extra pref code named
> "ui.osk.debug.keyboardDisplayReason" with the value "IKPOS: Touch screen not
> found.".

This is unrelated, it just means that the widget code (internal to Firefox) decided not to fire up the onscreen keyboard because the machine doesn't have a touchscreen.

What specific machine is this happening on? Can you reproduce on, say, the photon reference hardware?

	Cristian Comorasu, QA [:ccomorasu], Releae Desktop QA - Please contact mboldan@mozilla.com Reporter
	Comment 17 • 7 years ago

On my working station, do you require it's specifications?
I tried to reproduce with a photon reference hardware and it did not reproduce, not quite sure the hardware is causing this crash.

	Jim Mathies [:jimm]
	Comment 18 • 7 years ago

Was this reproduced using zip builds or an install? Can you test after a pave-over install to see if it fixes the problem?

	Cristian Comorasu, QA [:ccomorasu], Releae Desktop QA - Please contact mboldan@mozilla.com Reporter
	Comment 19 • 7 years ago

The issue occurred on a .zip format, however I tried the last couple of days to reproduce it on different environments and builds, it simply does not reproduce anymore. I will close this issue as works for me for now.