Browser Not responding after search when we clicked on newly opened tab before loading completely

RESOLVED INCOMPLETE

Status

()

--
critical
RESOLVED INCOMPLETE
3 years ago
3 years ago

People

(Reporter: mahesh.lokare7, Unassigned)

Tracking

({hang})

38 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [close me 2016-05-13])

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20160315145633

Steps to reproduce:

1. Open Firefox 
2. Go to Google.com
3. Search for anything
4. From search result Click on any two or more results back to back to  open in new tab in same browser window 
5. Before complete loading of newly opened tabs click on any of the tab


Actual results:

Browser stops responding we need to close it forcefully and restart or if it automatically closed will ask for restore message then we need to restore but restoration will also not solve the problem


Expected results:

tab should be opened successfully without causing browser crash
(Reporter)

Updated

3 years ago
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64
Version: 33 Branch → 38 Branch

Comment 1

3 years ago
https://developer.mozilla.org/en-US/docs/How_to_Report_a_Hung_Firefox
Severity: normal → critical
Keywords: hang

Comment 2

3 years ago
You have to test these 2 steps:
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

Is it reproducible in both cases?
Flags: needinfo?(mahesh.lokare7)
Whiteboard: [close me 2016-05-13]
Marking this as Resolved: Incomplete due to the lack of response from the reporter.
If anyone can still reproduce it on latest versions, feel free to reopen the issue and provide more information.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Flags: needinfo?(mahesh.lokare7)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.