Firefox 50 not launching
See original GitHub issueI updated Firefox to current version 50. Unit tests started from a command prompt are working fine. If unit tests are run in TeamCity on an agent, I get the following error:
[JavaScript Unit Tests] [2016-11-17 16:19:00.167] [WARN] launcher - Firefox have not captured in 60000 ms, killing.
I am running grunt with karma 1.3.0, karma-firefox-launcher 1.0.0 and grunt-karma 2.0.0.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:19
- Comments:25 (4 by maintainers)
Top Results From Across the Web
Firefox won't start - find solutions - Mozilla Support
If Firefox previously worked but suddenly doesn't start, it may be due to some corrupt data in your settings. Uninstalling and reinstalling Firefox...
Read more >Firefox will not open at all, no matter how many times I click it.
1. Kill firefox.exe through the Task Manager, to open the taskmanager hit Win + R and enter taskmgr.exe in the window, hit enter,...
Read more >Firefox 50 on Win10 now refuses to open local files
FF50 on Win10 won't open local files, like file:///C:/Users/MN/Documents/something/index.html. It claims the file is inaccessible.
Read more >My firefox 50 sync is not working - Mozilla Support
Hi , today i tried to sign-in to my firefox sync account, but it wont going through and its saying working , and...
Read more >Mozilla Firefox ver. 50 not prompting user to install Java plug ...
I have downloaded and installed the JRE and JDK on the endpoint device, but still no luck getting Firefox to load it. I...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We have run into the same issue running on Windows under the Jenkins service.
Same problem when using TeamCity 10.0.4, but I have no problems running it locally.