Installing hang
Categories
(Firefox :: Installer, defect, P3)
Tracking
()
People
(Reporter: corb0046, Assigned: nrishel)
Details
Attachments
(4 files)
Untitled2.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36 OPR/108.0.0.0
Steps to reproduce:
This has happened repeatedly 64 bit install of firefox
Actual results:
Install hangs then crashes, like its trying to install an active background process in Microsoft taskmgr but this version of windows is not allowing it..thats the impression i get...
Windows 11 Pro (non-activated key) version 23H2 OS build 22631.3296
Expected results:
should have completed the install with hang or crash with bug report
|
||
Comment 2•2 years ago
|
||
Thank you for the report. Moving this to the installer component so that team can take a look, though it looks like perhaps the crash reporter is for when we try to run Firefox near the end of the install.
Does the install complete and can you start Firefox after that?
Also, did you intentionally mark this as a security bug?
|
||
Updated•2 years ago
|
|
|
||
Comment 3•2 years ago
|
||
Marking as a P2 / S2. Waiting for feedback from the user. Will downgrade if we don't receive feedback within a day or two, or if it's not reproducible.
I can't reproduce this with the Firefox 124 release on Windows 11 Pro, 24H2. The installer runs and Firefox runs fine after it.
Need more info to proceed.
|
Assignee | |
Comment 4•2 years ago
•
|
||
I believe this is the relevant the crash report. n.b. default-browser-agent.exe is a thin wrapper that calls firefox.exe --backgroundtask defaultagent .... In this case it does some other logic in default-browser-agent.exe but we would not expect the relevant logic to hang, whereas we have an existing crash report that matches the description for the Firefox background task that would have also run at this time. Edit: The linked crash report would only be tangentially related if at all, as the relevant XPCOM object is not used when registering the scheduled task. Curiously though the background task was run immediately after installation and seemingly timed out (so maybe still related)?
:mhughes we might consider dropping to P3 S3. This doesn't impact many users - there's been no spike in crash reports and it's not immediately reproducible.
Yes there have prob been 500 bug crash reports sent on this, and nothing was done about it this started about 4 -5 months back…it’s gotten to the point where I had to create this cause it’s super annoying, even after it’s installed it creates a crash report…and I’ve never had any issues with Firefox EVER!..
The installer does not complete but you can run Firefox afterwards….just a matter of time before I’m sure another crash report pops up…
Yes I believe this is a security bug when your on a financial website and you get a crash report popping up…, if you want to de_ escalate it that is fine,,,and another reason is I did send a couple emails to Firefox about this with no reply…
I can make a video tomorrow if you like, bed time for me now..
|
|
||
Updated•2 years ago
|
|
|
Assignee | |
Comment 6•2 years ago
|
||
|
|
Assignee | |
Comment 7•2 years ago
|
||
:corb0046 could you check Window's Event Viewer for entries related to "Firefox Default Browser Agent"? See Default Agent error.png for an example of what we need.
|
|
Assignee | |
Updated•2 years ago
|
I tried reinstalling today with both the full version downloaded and the online install download version, and they both worked…
All Microsoft updates were installed, ghostry was installed (blocking all set)…and my Firefox sync account was linked with no problems, and i logged off the desktop versions that are not being used, in case that was causing in issue…so perhaps this is a hack issue with visiting certain websites or memory buffer issue….i have had issues with Firefox not closing down all the way and leaving instances of itself in the task manager background process, of which sometimes you are not able to kill it, without rebooting your computer…but today every is fine, install was ok, stability was ok and shutting it down was ok…..so I have no idea….i guess de-escalate this for now……I will try to make a video of when it happens but today nothing happened…so maybe it’s not a Firefox or windows issue, but a hacker issue..I cannot say, yesterday it hanged from the same file.the only difference is sometimes I switch to different win 11 versions which I restore from macrium.. backups, ie one for gaming and one for business..
Also Firefox was NOT set to default browser….maybe this happens when I set it to default browser,,,,I will test this out later
|
|
Assignee | |
Comment 10•2 years ago
|
||
Thanks for the check in. I do still need you to check of the Window's Event Viewer (see example here). Without that it's unlikely that I'll be able to answer whether the original problem was an issue in Firefox that can be fixed.
|
Reporter | |
Comment 11•2 years ago
|
||
i recorded the windows event viewer, im not sure how to find firefox logs cause there was none, assuming im using the right app?
I might have figured what is causing this...When i insalled on my business build its using a stable older version of Comodo firewall.
om my gaming build, im using beta 3 comodo firewall, I think the antivirus is blocking firefox code from being installed, i will test this out for tommorow... i made 2 videos showing the errors and bugs during the install, im not sure what data you want from windows event viewer?
let me know what else you want to see?
|
|
Reporter | |
Comment 12•2 years ago
|
||
sorry i upadated obs and the settings are messed up for the resolution i will make 2 new ones
|
|
Reporter | |
Comment 13•2 years ago
|
||
here are videos i made showing the install working with no issues so no idea it might not be comodo beta 3?
|
|
Assignee | |
Comment 14•2 years ago
|
||
It could be related but it's hard to tell at this point.
It was blurry but I didn't see what I was looking for in the Event Viewer (which is useful information). Could you open about:crashes in Firefox (typed into the URL bar like any website) and let me know the Report ID for any recent crashes (say in the past week)? If the reports are unsubmitted then could you also submit them? Screenshot or video of the page works if that's your preference. :)
|
|
Reporter | |
Comment 15•2 years ago
|
||
Yeah I’ll try to repeat bit again, today sometime…..it’s like a ghost bug, sometimes it happens and sometimes it doesn’t…I fixed the resolution in obs
Because you couldn’t even read nothing in the last videos…
|
|
Assignee | |
Comment 16•2 years ago
|
||
You should be able to find the existing bug reports in about:crashes from previous crashes without recreating it. If you can go there and let me know what the Report IDs are (and click submit on any report marked unsubmitted) I should be able to inspect the report on my side which should provide some clues.
|
|
Reporter | |
Comment 17•2 years ago
|
||
sorry not sure where to find the crash report at?
i made a new video on the business windows build and did the same hang now on this one,,im still thinking comodo is doing something..
just fyi i delete the drive every night and restore with same new build...so the logs will prob not be there from previous crashes,,,and im not really sure where to find the crash log you need?
|
|
Assignee | |
Comment 18•2 years ago
|
||
|
|
Assignee | |
Comment 19•2 years ago
|
||
Here's how you find the crash Report IDs.
You're correct, if you delete the drive nightly you'll need to recreate the bug to have any Report IDs to share.
|
|
Reporter | |
Comment 20•2 years ago
|
||
this is a legitimate one from an actual crash while installed im not sure if this was a hang during install or not from a while back,,,but it was also crashing constantly on / off after it was installed...
a99d4f0d-652c-4c50-a7eb-8a3947bd2164 2/4/2024, 5:34 PM
|
|
Reporter | |
Comment 21•2 years ago
|
||
|
|
Reporter | |
Comment 22•2 years ago
|
||
and there is still another issue of Firefox remaining in the background process from task manager, and un-able to close it when right clicking the firefox icon,,,this has been going on for YEARS!....
|
|
Assignee | |
Comment 23•2 years ago
•
|
||
It doesn't look like the a99d4f0d-652c-4c50-a7eb-8a3947bd2164 crash report was ever submitted (it should have been here), could you click the submit button for it (see prior image)?
|
|
Reporter | |
Comment 24•2 years ago
|
||
|
|
Reporter | |
Comment 25•2 years ago
|
||
there was one more crash today even though the app was supposed to be closed, i guess it was still open in task manager, background processes, and could not be close without a reboot of the OS....but i submitted these logs as well today 3-24-24
https://crash-stats.mozilla.org/report/index/f5c408f6-675a-4c75-80f6-4d8030240324
https://crash-stats.mozilla.org/report/index/15b317fd-ff39-4f52-a6d7-0f87d0240322
this crash happend before i updated to the newly released update.....
i will post the youtube vid as well for this..
|
|
Reporter | |
Comment 26•2 years ago
|
||
|
|
Assignee | |
Comment 27•2 years ago
•
|
||
For some reason your system really doesn't like Firefox Background Tasks (utilities that run things like update or file cleanup even when Firefox is closed. It's quite possible the it relates to comodo, but in an ideal world we wouldn't crash even if it were breaking something for us (and in general the crash reporter is not supposed to show for Background Tasks).
We'll need to read through the crash reports and see if there's a pattern; hopefully we can at least resolve the unnecessary pop-up if not the crash. For now I don't think we need any more crash reports/videos.
|
|
Reporter | |
Comment 28•2 years ago
|
||
yeah i installed firefox updated version today, and didnt have any install issues, and didnt hang in the bacground process after it closed, and didnt crash at all...do maybe they fixed it, with the last patch
|
|
Assignee | |
Comment 29•2 years ago
|
||
In that case it's fairly unlikely we'll be able to triage any further, but I think your thought that there was a bad interaction with antivirus seems likely.
Closing for now as INVALID as we suspect the issue was antivirus, we can reopen if it comes back.
Description
•