-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not launch IE #642
Comments
IE 10 launches 32 bit, then closes and launches 64 bit...which messes with karma, so we must point karma to execute 64 bit directly. The following steps fixed the capture problem for me on Windows 7 - 64 bit - IE 10:
I did NOT have to add localhost to my local intranet zones sites, but I'm sure it wouldn't hurt. This does NOT solve the problem of extra IE 32 bit processes being spawned, even though we are pointing karma to launch IE 64 bit directly. This is a big problem because with every CI build there is a new process taking up CPU and memory. |
Please move this to the https://github.com/karma-runner/karma-ie-launcher project. Review the issues there to see if one covers your situation first. |
moved it to karma-runner/karma-ie-launcher#6 |
@vojtajina - This can be closed. |
I'm still having this issue with IE11 on Windows 8.1. The proposed solutions here are not working for me with IE. Are there any updates to this? |
See karma-runner/karma-ie-launcher#6. That is where discussion of this has moved. |
Hi,
I have the same issue.
OS: Win 7 x 64
Karma: v0.9.3
Grunt:grunt-cli v0.1.9
grunt v0.4.1
I am getting error below:
WARN [config]: "/" is proxied, you should probably change urlRoot to avoid conflicts
INFO [karma]: Karma v0.9.3 server started at http://localhost:9876/
INFO [launcher]: Trying to start IE again.
ERROR [launcher]: Cannot start IE
INFO [launcher]: Trying to start IE again.
ERROR [launcher]: Cannot start IE
INFO [launcher]: Trying to start IE again.
ERROR [launcher]: Cannot start IE
I set the path to IE_BIN to C:\Program Files (x86)\Internet Explorer\iexplore.exe
http://localhost is added to Local Intranet zone and Protected mode is disabled.
The issue is still happening.
I looked at:
#605
#369
#429
Please advise
The text was updated successfully, but these errors were encountered: