Closed
Bug 1313059
Opened 9 years ago
Closed 9 years ago
Extremely slow startup and sometime crash on Win10 64bit, Nightly52.0a1 32bit Debug Build
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox49 | --- | unaffected |
firefox50 | --- | unaffected |
firefox51 | --- | unaffected |
firefox52 | --- | fixed |
firefox53 | --- | fixed |
People
(Reporter: alice0775, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
Attachments
(1 file)
88.13 KB,
text/x-log
|
Details |
Extremely slow startup and sometime crash on mozilla-central-win32-debug build.
The problem appears since Nightly52.0a1 32bit Debug build
https://hg.mozilla.org/mozilla-central/rev/8b2d92343bcb398075c909c587ec020286528059
20161019080022
Steps To Reproduce:
1. start firefox.exe -no-remote -P
2. Choose profile that no addon (almost clean)
3. Optionally, type something in locationbar
Actual Results:
about:home would not load forever.
sometimes hang and crash.
Regression window(m-c win32 debug):
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=03e795912fdbb000ac95f040d84e26d3eaa8c20a&tochange=8b2d92343bcb398075c909c587ec020286528059
Regression window(autoland win32 debug):
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=d74a9133f9a5c0a7374bef2a0be15e3ed7b37113&tochange=41d7a4864f3325cd9abcc5c5a17788334c8ca863
Regressed by: Bug 1310788
![]() |
Reporter | |
Updated•9 years ago
|
Summary: Extremely slow startup and sometime crash on Win10 64bit Nightly52.0a1 32bit Debug Build → Extremely slow startup and sometime crash on Win10 64bit, Nightly52.0a1 32bit Debug Build
![]() |
Reporter | |
Comment 1•9 years ago
|
||
user_pref("accessibility.force_disabled", 1); seems to fix.
Component: Untriaged → Disability Access APIs
![]() |
||
Comment 2•9 years ago
|
||
Alice, do you have any crash reports associated with this in about:crashes?
![]() |
Reporter | |
Comment 3•9 years ago
|
||
I am not familiar WinDbg. But, I attached log.
Updated•9 years ago
|
Whiteboard: aes+
Updated•9 years ago
|
status-firefox49:
--- → unaffected
status-firefox50:
--- → unaffected
![]() |
||
Comment 4•9 years ago
|
||
I tried yesterday and couldn't reproduce this locally on windows 10. I tried using IME, on screen keyboard, and ATs (separately)... but now I'm realizing this is a debug only behaviour? (I tried non-debug)
Is it possible to capture a cleopatra profile?
![]() |
Reporter | |
Comment 5•9 years ago
|
||
(In reply to David Bolter [:davidb] from comment #4)
> I tried yesterday and couldn't reproduce this locally on windows 10. I tried
> using IME, on screen keyboard, and ATs (separately)... but now I'm realizing
> this is a debug only behaviour? (I tried non-debug)
Yep, debug build only.
>
> Is it possible to capture a cleopatra profile?
Content process takes 100% core.
Initial page(about:home) is never finish.
And Gecko Profiler tool button is also unresponsive. So, I cannot get the cleopatra log.
Updated•9 years ago
|
Whiteboard: aes+
![]() |
Reporter | |
Comment 6•9 years ago
|
||
![]() |
Reporter | |
Comment 7•9 years ago
|
||
If set startup page to about:blank instead of about:home, the browser is start normal speed.
However, then open webpage(e.g https://developer.mozilla.org/en-US/Add-ons/Code_snippets), the browser becomes hangup and sometimes tab crashes.
So, now, the debug build is unusable.
Anyway, this is debug build only.
Severity: normal → minor
Comment 8•9 years ago
|
||
That crash is a ShutDownKill crash like the ones being reported in bug 1279293. I'm not yet sure if/how this is related, so I'm not duping yet.
![]() |
Reporter | |
Comment 9•9 years ago
|
||
(In reply to Aaron Klotz [:aklotz] from comment #8)
> That crash is a ShutDownKill crash
because browser is hang/unresponsive all the time. I must kill browser. That is a miracle report.
Comment 10•9 years ago
|
||
I cannot reproduce this on my Surface Book with 32-bit Nightly. I am rebuilding with 64-bit and will try again.
![]() |
Reporter | |
Comment 11•9 years ago
|
||
(In reply to Aaron Klotz [:aklotz] from comment #10)
> I cannot reproduce this on my Surface Book with 32-bit Nightly. I am
> rebuilding with 64-bit and will try again.
Probably, installing IME or something accessibility device is needed to reproduce this.
Comment 12•9 years ago
|
||
The surface book has a touchscreen and a screen keyboard. I'm starting there. If that doesn't work then I'll move up to IME and screen readers.
Comment 13•9 years ago
|
||
Any updates here, Aaron?
status-firefox53:
--- → affected
Flags: needinfo?(aklotz)
Comment 14•9 years ago
|
||
Hi Alice, I assume this is still happening for you?
Flags: needinfo?(alice0775)
![]() |
Reporter | |
Comment 15•9 years ago
|
||
Reproduced on the bad build nightly52.0a1 debug ID:20161019080022
https://hg.mozilla.org/mozilla-central/rev/8b2d92343bcb398075c909c587ec020286528059
Verified to fix on nightly53.0a1 debug ID:20170109122607 https://hg.mozilla.org/mozilla-central/rev/0f9d69253ac67887b64f5efeffaebebb5929b1a7
and aurora52.0a2 debug ID:20170109140908 https://hg.mozilla.org/releases/mozilla-aurora/rev/10e1849db4be083d35c4e40a7d7a7b32a0437817
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(alice0775)
Resolution: --- → FIXED
![]() |
Reporter | |
Updated•9 years ago
|
Flags: needinfo?(aklotz)
Comment 16•9 years ago
|
||
Thanks!
You need to log in
before you can comment on or make changes to this bug.
Description
•