I'm not actually trying to spin off a renderer. I'm creating a watchdog program that acts as a crash service for creating dumps, logging to a file, and informing the user via a msg box (based on crash_service.cc). It then restarts the process that crashed. i don't have to worry about the non-interactive desktop (as I simply won't call TargetPolicy::SetDesktop()).
I like the power of the chromium's policy based sandboxing, so i'd like to use it (i especially like the hooks for unloading blacklisted DLLs and and function patching). that said, maybe there's a better/ simpler way? On Mar 11, 5:02 pm, cpu <[email protected]> wrote: > As darin/adam said, the right way is with an ipc message. But I am > curious, what do you want to do? > > If it is for debugging purposes you can just start chrome with --no- > sandbox. > > If you want to have dialog boxes pop directly controlled by the > renderer, you will be fighting the architecture of chrome. > > Not only you would need to access to the desktop window but before > that have a handle to the interactive desktop. That is, the entire > renderer is connected to a desktop that is not "winsta0\default". In > other words even JOB_OBJECT_UILIMIT_HANDLES is not sufficient. > > Finally, you don't want to call MessageBox from one of chrome's > threads. This would enter the thread in a nested message loop that the > rest of chrome is not aware of. Bad stuff would happen in short order. > This also applies if you are using --no-sandbox. > > On Mar 11, 4:50 pm, Adam Langley <[email protected]> wrote: > > > On Wed, Mar 11, 2009 at 4:47 PM, DanielC <[email protected]> wrote: > > > Where might I find an sample demonstrating this? > > > The messages are defined in chrome/common/render_messages_internal.h. > > > The message ends up in > > chrome/browser/renderer_host/browser_render_process_host.cc (look for > > the dispatch table, full of macros). > > > The message is sent via chrome/renderer/render_thread.h::Send. > > > AGL --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
