When using PhantomJS 1.7.0 on Windows 8 the process never exists and will just hang.
What steps will reproduce the problem? 1. From a cmd.exe prompt run phantomjs.exe -v 2. It will print out 1.7.0 and hang 3. Notice Ctrl-C doesn't do anything.
I am using the static Windows build of PhantomJS 1.7.0
Comment #1
Posted on Oct 29, 2012 by Quick CamelLooking into this further I am only able to reproduce this on two Windows 8 machines. On others it is working fine. I am still investigating what machine specific differences could cause this.
Comment #2
Posted on Oct 29, 2012 by Quick MonkeyCan you create a crash dump when PhantomJS hangs?
You can do it by using ProcDump (http://technet.microsoft.com/en-us/sysinternals/dd996900) Download it, run phantomjs, wait until phantomjs will hang, and then execute the following command to generate a crash dump:
procdump.exe -ma phantomjs
Comment #3
Posted on Oct 30, 2012 by Quick CamelHere is a link to the dump: http://sdrv.ms/TrmJSY It was too big to attach.
Comment #4
Posted on Oct 30, 2012 by Quick MonkeyI was unable to reproduce this issue on Win 8.
Comment #5
Posted on Nov 18, 2012 by Happy CatI see the same behavior using Windows 8 RTM build. It runs my tests from the command line, then never exits.
Comment #6
Posted on Nov 29, 2012 by Quick RhinoI'm having the same issue. With 1.6.1 it just crashes and with 1.7 it hangs. This on Windows 8 RTM
Comment #7
Posted on Nov 29, 2012 by Quick MonkeyInteresting. Unfortunately, I was unable to reproduce this on a clean installation. Is there any special condition (or something else) that could help me to reproduce this issue?
Comment #8
Posted on Nov 29, 2012 by Quick RhinoTrying to debug I am getting this error: "Unhandled exception at 0x74CFCE39 in phantomjs.exe: 0xC0000005: Access violation executing location 0x74CFCE39."
Not sure if this will help.
Comment #9
Posted on Nov 29, 2012 by Quick Monkey1.6.1 version has no error handling. It was introduced in 1.7.
Could you provide me a dump when 1.7 hangs? You can find instructions in my comment #2 (http://code.google.com/p/phantomjs/issues/detail?id=845#c2)
Comment #10
Posted on Nov 30, 2012 by Quick RhinoSure here it is: http://sdrv.ms/WyaNgm
Comment #11
Posted on Nov 30, 2012 by Happy CatComment deleted
Comment #12
Posted on Nov 30, 2012 by Happy CatYou should be able to repro this issue using this:
https://github.com/billyzkid/phamine
Clone this small repository, cd into it, and then execute the following command:
lib\phantomjs-1.7.0-windows\phantomjs.exe src/phamine.coffee sample/SpecRunner.html
In my tests, everything works perfect on Windows 7 every time -- the tests run and PhantomJS exits correctly. On Windows 8, however, the tests runs correctly, but PhantomJS never exits, so I can't get my command prompt back.
Comment #13
Posted on Nov 30, 2012 by Quick MonkeyFail. I wasn't able to reproduce. PhantomJS exits normally.
- win8_phantomjs_170.png 37.34KB
Comment #14
Posted on Dec 1, 2012 by Happy CatWeird. Maybe this is a sinister machine specific issue like Comment 1 suggests. It happens for me every time and I can't figure out a workaround and this is a pretty minimal example.
I will try on another Win8 machine. Can anyone else try?
Comment #15
Posted on Dec 1, 2012 by Happy CamelI have the very same problem, but don't really know how to help in investigating the problem. 1.6.1 crashes every time, and 1.7.0 hangs every time.
Comment #16
Posted on Dec 1, 2012 by Quick MonkeyYou can help me by providing a crash dump when 1.7.0 hangs. See my comment #2 http://code.google.com/p/phantomjs/issues/detail?id=845#c2
Comment #17
Posted on Dec 3, 2012 by Happy CamelOK, here's the dump: https://dl.dropbox.com/u/7884905/Permanent/phantomjs_121203_094536.dmp
I used billyzkid's phamine example for creating it.
Comment #18
Posted on Dec 3, 2012 by Quick MonkeyThanks! Quick analysis gave me that those hangs are caused by Nvidia drivers (specifically by nvinit.dll library). Very strange issue.
Did you have two graphical cards on machines, for example Intel and NVidia?
Comment #19
Posted on Dec 3, 2012 by Quick RhinoI can confirm. I have Intel HD and NVidia driver under device manager. When disabling NVidia driver it does not hang.
Comment #20
Posted on Dec 3, 2012 by Quick MonkeyI'm assuming you need to try a new NVidia driver version :)
Comment #21
Posted on Dec 4, 2012 by Happy CatComment deleted
Comment #22
Posted on Dec 4, 2012 by Happy CatComment deleted
Comment #23
Posted on Dec 4, 2012 by Happy CatComment deleted
Comment #24
Posted on Dec 4, 2012 by Happy CatComment deleted
Comment #25
Posted on Dec 4, 2012 by Happy CatComment deleted
Comment #26
Posted on Dec 4, 2012 by Happy CatI also have display adapters for both Intel HD Graphics and NVidia NVS 3100M. Here's what I've discovered.
a) Updating to the very latest NVidia driver did not fix the hang.
b) If I disable NVidia, then PhantomJS no longer hangs. If I re-enable NVidia, then it hangs again.
c) If NVidia is enabled, the hang will go away if I select "Integrated graphics" as the preferred graphics processor (NVidia Control Panel > Manage 3D Settings > Global Settings).
d) Surprisingly, if I select "High-performance NVidia processor", then the hang also goes way.
e) The only option that continues to hang is the default one ("Auto-select") which you would think would be the same as either c) or d) above.
So, it seems like this issue is caused by the auto-selection of a GPU.
Comment #27
Posted on Dec 7, 2012 by Quick CamelI can also confirm the same. I have both Intel and Nvidia drivers.
Comment #28
Posted on Dec 16, 2012 by Quick RabbitI don't think we can fix this. However, I'll make sure this is noted as Known Issues in the upcoming release notes.
Comment #29
Posted on Feb 9, 2013 by Swift CatSame here: selecting "High-performance NVidia processor" helped resolving the issue (of PhantomJs 1.8.1 hanging). OS: Windows 7 64 bit Ultimate. CPU: Intel Core i7-3610QM (2.30GHz)(2.30GHz) RAM: 8 GB
- NVidia with Auto-select.png 48.14KB
Comment #30
Posted on Mar 16, 2013 by Happy HorseThis issue has been moved to GitHub: https://github.com/ariya/phantomjs/issues/10845
Comment #31
Posted on Oct 28, 2013 by Quick BirdWhy does this problem only occur in Visual Studio 2013 and not in Visual Studio 2012 on the same machine if it is a video driver issue?
Status: WontFix
Labels:
Type-Defect
Priority-Medium
Milestone-Release1.8