Closed Bug 1414004 Opened 7 years ago Closed 10 months ago

Unable to open Nightly - Process is opened in Task Manager

Categories

(Toolkit :: Startup and Profile System, defect)

58 Branch
x86
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: theoramiro, Unassigned)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
Build ID: 20171101220120

Steps to reproduce:

When I open the laptop (Alienware 17 R4) and try to open Mozilla Nightly, it opens the process (when it requires updates, it installs them) but not the actual browser. 


Actual results:

The process is opened in Task Manager and if I try to open Nightly again, it opens another process (every time I try to open the browser it creates another task), but the browser does not appear (neither in the task bar, nor on the screen). 
Workaround: If I close the task (or in the case that I open multiple processes by trying multiple times to open the browser) and after that open Nightly, it opens as normal and no additional issues occur. 


Expected results:

It should open the browser and not only the process. 

Thank you. :)
OS: Unspecified → Windows 10
Hardware: Unspecified → x86
I tried to close the browser because it was consuming ~7,5 GB of RAM with only 8 tabs opened.
When I tried to open it again, same issue as in the description occurred (the browser didn't open but the process did). 
Also I don't find it normal for so much RAM to be consumed. 
Until now I never checked how much RAM was consumed while using the browser. 
I will provide an update when I notice any additional issues.
Please find attached some basic troubleshooting made with Safe Mode.
May I ask for you to be more specific regarding what is needed? 

Additionally, how can I do some performance testing on Nightly? I don't have the necessary time to try some heavy load using Safe Mode.
Dears,

At the very moment it seems that the incident created by me does not raise any concerns and the issue still exists on my side. I was more interested in being part of what seemed to be a very nice community when it comes to testing and making the browser user friendly and accessible. I am working as a junior QA specialist and thought that helping around, in my free time, will make this browser maybe better, additionally also helping me learn new things regarding the testing field (as I never tried to test a browser before). 

The fact that nobody bothered to respond to my incident, nor properly explain what troubleshooting steps would be required from my side has given me the idea that this community is not what I expected. 

Thank you for your reply and maybe I will come back to this browser when it will be more mature and not have so many issues. 

Best regards,
Theodor.
Severity: normal → critical
Component: Untriaged → Startup and Profile System
Product: Firefox → Toolkit

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: critical → --

The severity field is not set for this bug.
:mossop, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(dtownsend)

Is this still happening with a recent version of Firefox? I believe we have resolved a few bugs that may have been the cause of this.

Flags: needinfo?(dtownsend) → needinfo?(theoramiro)

Redirect a needinfo that is pending on an inactive user to the triage owner.
:mossop, since the bug has recent activity, could you please find another way to get the information or close the bug as INCOMPLETE if it is not actionable?

For more information, please visit BugBot documentation.

Flags: needinfo?(theoramiro) → needinfo?(dtownsend)
Status: UNCONFIRMED → RESOLVED
Closed: 10 months ago
Flags: needinfo?(dtownsend)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: