You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which program triggers the problem? Specify the filename if possible.
latest Dev Google chrome 5.0.375.9, or latest chromeplus 1.3.9.0
The version number does not matter, the problem is there for a long time.
What steps will reproduce the problem?
1. Start the browser after a fresh start of PC, with high probability, an
error box bumps in, saying chrome.exe crashed.
or
1. Even if I can start the browser successfully, after some time of idle, I
cannot create new tab. When I press Ctrl+N, a tab with blank content
appears. The new tab does not try to connect any url. However, existing tab
is totally normal.
What is the expected output? What do you see instead?
What version of gdipp are you using? On what operating system (bitness)?
All the versions to 0.7.5 on x64 windows Ultimate
Please provide any additional information below.
The problem is not related to addons. A fresh google chrome or chromeplus
has the problem. Chromeplus is portable.
Original issue reported on code.google.com by DCatcher...@gmail.com on 22 Apr 2010 at 3:56
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 crendk...@gmail.com on 22 Apr 2010 at 9:14
Original issue reported on code.google.com by
DCatcher...@gmail.com
on 22 Apr 2010 at 3:56The text was updated successfully, but these errors were encountered: