Hello, I'm working on supporting multiple X displays (http://crbug.com/15781). I've modified process_singleton_posix.cc to forward the display name back to the host which then pushes it all the way to browser_window_gtk.cc and assigns the browser window to that display. That part seems to work, the browser window appears on the local display. But the host process immediately dies with a cryptic X error:
The program 'chrome' received an X Window System error. This probably reflects a bug in the program. The error was 'BadDrawable (invalid Pixmap or Window parameter)'. (Details: serial 1972 error_code 9 request_code 62 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) I've tried a few things to break on that function and get a stack trace in gdb, but nothing seems to work. Neither --renderer-cmd-prefix='gdb --args' nor modifying zygote to always append --sync to the forked chrome process worked. I'm not sure what to try next. I'm on hardy (64-bits), would compiling 32-bit versions of glib and gtk be worth it? Any other ideas? Thanks! Albert --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
