Please mention OSX fix for issue #4 in documentation
tararoys opened this issue · 3 comments
Trying to run Chrome on OSX with the flag mentioned in the "Cross domain policy problems under Chrome" section of the README. resulted in the following error:
> /Applications/GoogleChrome.app/Contents/MacOS/GoogleChrome --allow-file-access-from-files SpecRunner.html
[29978:2819:0211/221357:ERROR:process_singleton_mac.cc(103)] Unable to obtain profile lock.
After three solid hours of debugging, the magic solution was to close Chrome entirely. Without an instance of Chrome running, the profile lock (not certain what a profile lock is, but this guy seems to know is no longer a problem, and you can run the command:
>/Applications/GoogleChrome.app/Contents/MacOS/GoogleChrome --allow-file-access-from-files SpecRunner.html
And Chrome will allow you to load fixtures just fine.
note: for people who are trying to use the path /Applications/GoogleChrome.app/Contents/MacOS/GoogleChrome to launch Google Chrome, be warned that the spaces in the default name annoyed me so renamed "Google Chrome" to GoogleChrome. You probably want to check to see what your personal pathname is.
so add something that says that you need to quit a running chrome before running that command to open a new one?
Yes. Specifically, you need to completely close Chrome as a program, because that will release the profile lock. (I don't know what a profile lock is. I just know that it turns on whenever you start chrome and prevents you from opening a new chrome window with the allow-file-access-from-files flag.)
This feels super hacky.. is there no better way to build this into the library?