Google Chrome 9

v.laurie · 04. Feb 2011, 03:08 AM

Google has released version 9 of the Chrome browser: http://chrome.blogspot.com/2011/02/d...-and-apps.html

emmjay · 05. Feb 2011, 02:29 PM

I installed Chrome 9 yesterday. When I opened it outside SBIE, it was fine, however when I opened it with SBIE, I got a BSOD, with the error 'Bad Pool Header'.

Rebooted W7 ... all OK. In MS Technet, 'Bad Pool Header' stop error is considered memory corruption or driver error. Running 'Driver Verification' produced nothing and 'Mem86' produced no errors.

I also ran' extensive hardware tests' using PC Doctor after that ... all tests passed.

This may or may not be related to SBIE ... I do not know. There may be a compatibility problem here, but again I do not know. I will watch the Chrome forum over the next couple of days to see if anybody else runs into this. If there are no posts, then I will considered it an isolated error that needs further investigation at my end. I have excluded Chrome.exe from SB for the short term.

v.laurie · 05. Feb 2011, 04:24 PM

Quote:

Originally Posted by emmjay

I installed Chrome 9 yesterday. When I opened it outside SBIE, it was fine, however when I opened it with SBIE, I got a BSOD, with the error 'Bad Pool Header'.

Chrome is already sandboxed. perhaps there was a conflict?

garth · 05. Feb 2011, 04:52 PM

Quote:

Originally Posted by v.laurie

Chrome is already sandboxed. perhaps there was a conflict?

Chrome has sandboxing built in? I never knew that.
I experienced a similar bsod event when i opened a sandboxed browser while BufferZone was running and have concluded that it's best (for me) to have one virtualisation app on one machine, and have settled on Sandboxie. That said, i've never seen my machine shut down so fast

v.laurie · 05. Feb 2011, 07:53 PM

The gory details of Chrome sandboxing are at this link https://sites.google.com/a/chromium....ox/Sandbox-FAQ

garth · 05. Feb 2011, 08:03 PM

Quote:

Originally Posted by v.laurie

The gory details of Chrome sandboxing are at this link https://sites.google.com/a/chromium....ox/Sandbox-FAQ

Thanks for that

emmjay · 09. Feb 2011, 04:55 PM

There are a couple of posts on the Chromium forum site from users who are getting BSODs (Bad Pool Header stop error). However, as the posters have not indicated what was running when this happened I am not convinced, at this time, that it is related to having SBIE on the browser. I submitted a post to see if the support staff have encountered it or not. Will update if I find anything else about this.

emmjay · 10. Feb 2011, 04:50 PM

I got a PM on this from an SBIE poster .. we talked about what I had installed and the most helpful responder suggested I uninstall Spyshelter and reinstall SBIE 3.5.2.
I have since done this and I have had no problems with opening Chrome 9 with SBIE.

George · 11. Feb 2011, 04:40 PM

Is it still using IE proxy settings?

04. Feb 2011, 03:08 AM	#1 (permalink)
v.laurie Editor Join Date: Jul 2010 Posts: 202	Google Chrome 9 Google has released version 9 of the Chrome browser: http://chrome.blogspot.com/2011/02/d...-and-apps.html

11. Feb 2011, 04:40 PM	#9 (permalink)
George Progradminstrateditor Join Date: May 2008 Location: Frankfurt, GER Posts: 1,253	Is it still using IE proxy settings? __________________ Best regards, George

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

05. Feb 2011, 02:29 PM	#2 (permalink)
emmjay Senior Member Join Date: Dec 2009 Posts: 226	I installed Chrome 9 yesterday. When I opened it outside SBIE, it was fine, however when I opened it with SBIE, I got a BSOD, with the error 'Bad Pool Header'. Rebooted W7 ... all OK. In MS Technet, 'Bad Pool Header' stop error is considered memory corruption or driver error. Running 'Driver Verification' produced nothing and 'Mem86' produced no errors. I also ran' extensive hardware tests' using PC Doctor after that ... all tests passed. This may or may not be related to SBIE ... I do not know. There may be a compatibility problem here, but again I do not know. I will watch the Chrome forum over the next couple of days to see if anybody else runs into this. If there are no posts, then I will considered it an isolated error that needs further investigation at my end. I have excluded Chrome.exe from SB for the short term.

05. Feb 2011, 07:53 PM	#5 (permalink)
v.laurie Editor Join Date: Jul 2010 Posts: 202	The gory details of Chrome sandboxing are at this link https://sites.google.com/a/chromium....ox/Sandbox-FAQ

09. Feb 2011, 04:55 PM	#7 (permalink)
emmjay Senior Member Join Date: Dec 2009 Posts: 226	There are a couple of posts on the Chromium forum site from users who are getting BSODs (Bad Pool Header stop error). However, as the posters have not indicated what was running when this happened I am not convinced, at this time, that it is related to having SBIE on the browser. I submitted a post to see if the support staff have encountered it or not. Will update if I find anything else about this.

10. Feb 2011, 04:50 PM	#8 (permalink)
emmjay Senior Member Join Date: Dec 2009 Posts: 226	I got a PM on this from an SBIE poster .. we talked about what I had installed and the most helpful responder suggested I uninstall Spyshelter and reinstall SBIE 3.5.2. I have since done this and I have had no problems with opening Chrome 9 with SBIE.