Closed Bug 811698 Opened 12 years ago Closed 7 years ago

Firefox hangs on dns resolution w/HTTPS Everywhere or HTTPS Finder

Categories

(Firefox :: Extension Compatibility, defect)

16 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: emmanuel.pierre, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20100101 Firefox/16.0 Build ID: 20121024073032 Steps to reproduce: Habitual web browsing, HTTPS everywhere module. I've had this for several versons now on Windows 7_64, I have this now on a new Linux 3.6.3_AMD64 Actual results: Firefox freeze (from several versions), when I click on another tab during the freeze, the tab is opened in a new window Expected results: freeze only in the current tab, no global freeze, no new tab open
Access: Pro-DSL, Cable internet
Could you test the basic troubleshooting steps, please: 1) Safe mode: https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode 2) New profile: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles (don't import anything) Do you observe the same issue about DNS resolution?
Flags: needinfo?(emmanuel.pierre)
Thanks for the indications. ok, seems there is no freeze anymore. There are some timeouts on massive page opening but no more freeze. Now from there, do I have to open/close modules to find which is the problem? A list of them: adblock autopager firebug dom inspector https finder https finder everywhere web developper session manager Thanks,
Flags: needinfo?(emmanuel.pierre)
OK modules without HTTPS finder or HTTPS everywhere works fine. But when I get one or the other back with multiple https page load in parallel, it hangs again so either it is the technologies behind those modules that have a common problem or this is an issue in the SSL level negociation in Firefow, your opinion ?
So one of these both extensions is likely the culprit. As you're forcing HTTPS, the issue is here. Just try to use your current profile without these modules.
Yes, without both of them this is fine, this is why I wonder about setting up SSL session in parallel as an issue
Well, if you can't reproduce the freezes without extensions just by using HTTPS, it's probably best to report the problem to the extension authors. If you can reproduce without those extensions, then it makes sense to track it in bugzilla, in which case we need more specific steps to reproduce. Possibly related: bug 738006, bug 738028, bug 644475.
Component: Untriaged → Extension Compatibility
Flags: needinfo?(emmanuel.pierre)
Summary: Firefox hangs on dns resolution → Firefox hangs on dns resolution w/HTTPS Everywhere or HTTPS Finder
Well, if you can't reproduce the freezes without extensions just by using HTTPS, it's probably best to report the problem to the extension authors. If you can reproduce without those extensions, then it makes sense to track it in bugzilla, in which case we need more specific steps to reproduce. Possibly related: bug 738006, bug 738028, bug 644475.
Hello, as those two bugs listed, I cannot reproduce them without the HTTPS extensions, I'll try to switch them on again to veryfy I have something similar or not.
Flags: needinfo?(emmanuel.pierre)
You don't have to try to reproduce them, it probably won't help with this bug. I have a slight hope that tweaking prefs noted in bug 738028 might help (in case this is caused by something in Firefox after all). (P.S. Please don't clear the needinfo flag by checking the 'I'm providing the requested information' box unless you think there's now enough information for someone to take another look at this bug. We're using it to avoid duplicate work among the people who go through the untriaged bugs.)
Flags: needinfo?
You don't have to try to reproduce them, it probably won't help with this bug. I have a slight hope that tweaking prefs noted in bug 738028 might help (in case this is caused by something in Firefox after all). (P.S. Please don't clear the needinfo flag by checking the 'I'm providing the requested information' box unless you think there's now enough information for someone to take another look at this bug. We're using it to avoid duplicate work among the people who go through the untriaged bugs.)
This is about a legacy extensions which are no longer valid in Firefox Quantum, closing.
Flags: needinfo?
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.