Skip to content
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

TermKit crashes on startup #32

Open
theromi opened this issue May 19, 2011 · 11 comments
Open

TermKit crashes on startup #32

theromi opened this issue May 19, 2011 · 11 comments

Comments

@theromi
Copy link

theromi commented May 19, 2011

When starting TermKit it shows up for a few seconds (unuseable, still seems to load, with a white background) and then crashes. "node termkit.js" is running.

Crashreport is here: https://gist.github.com/980495

roman-macbook:node roman$ node --version
v0.4.7

@hmottestad
Copy link

Is there anything is your logs? (console messages)

@theromi
Copy link
Author

theromi commented May 19, 2011

Nope, it doesn't seem to connect to node.

@billdozr
Copy link

I have the same problem when trying to run TermKit app.

Crash report: https://gist.github.com/980547

@hmottestad
Copy link

Maybe a firewall issue?

The crash report says EXC_BAD_ACCESS on CFArrayGetCount, which is probably an array out of bounds. There is a note of a proxy. Do you have a proxy set up?

@billdozr
Copy link

@hmottestad

You are quite right. Are there specific proxy instructions for TermKit or do I just have to just insure I just have http_proxy set?

@hmottestad
Copy link

I'm not sure. Try playing around with it and see what happens.

I'm using a proxy on my machine (glimmerblocker) and it's not having any effect. It's a simple http proxy. What proxy settings do you have?

@hmottestad
Copy link

Seems like it's a bug in webkit: https://bugs.webkit.org/show_bug.cgi?id=47450

@hmottestad
Copy link

Might be a problem with the "Automatic Proxy Configuration" in System Preferences, Network, Advanced, Proxies

@3rd-Eden
Copy link

Relates to: #7

@theromi
Copy link
Author

theromi commented May 19, 2011

Jup, "Automatic Proxy Configuration" is the problem, though I don't have any proxy to autodetect..

@billdozr
Copy link

Unchecking "Automatic Proxy Configuration" does fix the problem for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants