Call it "force-closing" or crashing, I just started using Chrome but most of the time the browser cannot fully open before NOD32 (22.214.171.124) closes it. The only way to get around it is to disable NOD32. If I do that I can browse, and then shortly after that I enable security on NOD32 again. There is a discussion going on here, but its way over my head: http://code.google.com/p/chromium/issues/detail?id=21715 I looked around this forum for other threads relating to this issue but found 0? Any help is appreciated.