1707150 - Firefox developer editor 64bit do not response ( freeze ) in MS win7 pro 64bit

Status: RESOLVED DUPLICATE of bug 1706219

(Firefox :: General, defect)

Description

[peter]

Attachment: TdvVozaSId.gif

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:89.0) Gecko/20100101 Firefox/89.0

Steps to reproduce:

1. Double click firefox developer editor icon to run it
2. try to input some url to browse web site ( for example www.google.com )

win7 pro service pack 1 ( 64bit )
cpu i3
ram 8G
firefox developer edition 89.0.0.7782 ( 2021/4/23 5:41AM )

I try to input url , click [close window] [add tabs] [menu] button , it's not working
the only working command is [close tab] , it will close ff. ( attach file )

Actual results:

does not go to web site

Expected results:

it should go to web site.

Comment 1

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Editor' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Liseta Esteves]

Also happens to me since yesterday.

Comment 3

[Emilio Cobos Álvarez [:emilio]]

[Tracking Requested - why for this release]: Seems like a severe regression, and multiple people seem to be experiencing it.

If you can reproduce this, it'd be extremely useful if you could use mozregression to figure out what broke this.

Comment 4

[Olli Pettay [:smaug][[e-mail]]]

Hmm, or rather, this doesn't sound like performance issue. Something to do with MR1?

Comment 5

[Liseta Esteves]

I already have my problem solved.
I went to Menu Help - More Troubleshooting Information, click 'about: profiles' on Profiles (Application Basics). I checked the Developer profile folder, deleted the profile and created a new one.

Comment 6

[Pascal Chevrel (relman team) -> :pascalc|PTO until Sept 2]

I am going to dupe that against bug 1706219 as I think it is the same issue. We have a fix coming in this bug. Once we have it landed and uplifted to the beta branch, please check that the issue is actually fixed, thanks.