Closed
Bug 1499291
Opened 7 years ago
Closed 7 years ago
freeze in xul.dll
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: github, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0
Steps to reproduce:
I've opened the Lotus Notes Webmail interfaces and tried to write an email.
Actual results:
Firefox did not respond to any keyboard input or to mouse clicks but the curser was still blinking.
I've created a wpr trace. The call stack leads to high cpu load in xul.dll.
The legacy extension Remote XUL Manager 1.3.2 is installed but disabled.
Comment 1•7 years ago
|
||
Hi,
Thank you for the feedback and for taking the time to report this. As I don't have a valid Lotus Notes Webmail account (user/pass) I can't reproduce this issue.
However there are a few things that we can try:
1. Could you please retest using safe mode (https://goo.gl/AR5o9d), maybe even a new clean Firefox profile (https://goo.gl/AWo6h8), to eliminate add-ons or custom settings as a possible cause.
2. If the issue reproduces after step 1. please download Firefox Nightly from here: https://nightly.mozilla.org/ and retest the problem.
3. If the issue is still reproducible in the latest Nightly, can you please also capture a performance profile (in Nightly)? You can get more info on how to install and use the Cleopatra add-on (that helps you get the performance profile) by going to:
https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler
https://perf-html.io/
Flags: needinfo?(github)
Comment 2•7 years ago
|
||
Hi,
Marking this as Resolved: Incomplete due to the lack of response from the reporter.
If the issue is still reproducible with the latest Firefox version, feel free to reopen the bug with more information.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Sorry for the late response. This bug is hard to reproduce so I cannot provide additional traces.
Flags: needinfo?(github)
You need to log in
before you can comment on or make changes to this bug.
Description
•