Google Chrome or Chromeplus acts wired

[GoogleCodeExporter]

Google Chrome or Chromeplus acts wired

[GoogleCodeExporter]

I myself experience this problem also. However, the error message is sent from
csrss.exe, not chrome.exe. This indicates that the source of problem may not be 
the
render engine bug the injection mechanism.

As probably many people know, Chrome features an extra security system called 
Sandbox
browsing. Each tab is spawned as a independent process. Internally, these 
processes
are high restricted. Example of the security is that directly accessing files 
on disk
is prohibited, like HIPS usually does. Due to the restriction, normal gdimm 
injection
will not work in Chrome.

I wrote a special injection function for Chrome. It is low-level assembly code 
and
lacks portability and error-checking. It is mostly working, but when something 
goes
wrong, the consequence can be hard to tell.

Since force injecting DLL to the sandboxed process may be considered as a 
security
breach, we may decide eventually remove the buggy code in the future and leave 
Chrome
un-rendered.

Original comment by [email protected] on 22 Apr 2010 at 9:14

[GoogleCodeExporter]

Original comment by [email protected] on 22 Apr 2010 at 9:21

• Changed state: Duplicate