Closed Bug 659146 Opened 14 years ago Closed 9 years ago

An external program (Spotify) launches Firefox. Firefox hangs (process runs, but no window)

Categories

(Firefox :: General, defect)

4.0 Branch
x86_64
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: cbramdit, Unassigned)

References

Details

(Keywords: hang)

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 cf. below Reproducible: Always Steps to Reproduce: 1. Install Spotify Open (https://www.spotify.com/get-spotify/go/open) 2. Launch Spotify 3. Close FF. Verify that the process terminates. 4. In Spotify's title bar, you will see a counter of the remaining time you have playing music (less than 10 hours). Click on that line/button. A drop-down list will appear. 5. Click on "Upgrade or learn more". It's supposed to show you the following web page: https://www.spotify.com/<YOUR_COUNTRY>/get-spotify/go/premium/?utm_source=spotify&utm_medium=messagebar&utm_campaign=upgrade_product 6. If FF is your default browser, it will be launched. The process runs, but the browser window does not appear. Actual Results: firefox.exe is started, but the browser window does not appear Expected Results: The browser window is opened. An extra tab is opened, displaying the web page https://www.spotify.com/<YOUR_COUNTRY>/get-spotify/go/premium/?utm_source=spotify&utm_medium=messagebar&utm_campaign=upgrade_product
Version: unspecified → 4.0 Branch
cbramdit, do you still see this problem?
Severity: normal → critical
Flags: needinfo?(cbramdit)
Keywords: hang
Whiteboard: [closeme 2016-09-15]
(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #3) > cbramdit, do you still see this problem? This is a very old bug. I suggest to close it.
Resolved per whiteboard and Comment 4
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(cbramdit)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2016-09-15]
You need to log in before you can comment on or make changes to this bug.