Closed GoogleCodeExporter closed 9 years ago
This is expected behavior. gdipp does not inject existing processes when
starting,
except explorer.exe in the current versions.
Original comment by crendk...@gmail.com
on 29 May 2010 at 5:09
No, no. It isn't when starting. gdipp is already started.
What I meant is: gdipp checks for new processes in within an interval of 1
second.
If I start google chrome and the process that renders the page is started
between two
checks, it is not reached by gdipp. The google chrome application is smoothed,
but
the webpage isn't. To perform a better check, increase the pool_interval value
to
5min and start google chrome.
Btw, is there any possibility of joining the development team?a
Original comment by ceduardo...@gmail.com
on 29 May 2010 at 2:12
I see. Chrome is an exception that the normal injection does not apply, thanks
to its
restricted sandbox. gdipp injects the page processes from the unrestricted UI
process
(which spawns the page processes). Therefore, if by the time the page processes
are
spawned when the UI process has not been injected yet, the page processes are
not
rendered. However, I think this is only a problem for the first homepage after
Chrome
starts. Or you mean something else?
I can add you to the committers if you wish to contribute. Is your gmail address
ceduardo.melo <at> gmail.com?
Original comment by crendk...@gmail.com
on 30 May 2010 at 4:31
This is exactly what I meant.
I would like very much to contribute. But since I still have no knoledge of the
codebase yet, will take some time to send my first contribution. And yes, that
is my
address. :D
Original comment by ceduardo...@gmail.com
on 30 May 2010 at 7:31
Original comment by crendk...@gmail.com
on 2 Jul 2010 at 4:06
Original issue reported on code.google.com by
ceduardo...@gmail.com
on 29 May 2010 at 12:19