We're taking guesses at the moment. I look at the backtrace and see that
WebKit dies deep inside, but it's not obvious how we're killing it.
Avi
On Wed, Mar 11, 2009 at 10:50 AM, Amanda Walker <awal...@google.com> wrote:
> Do we know it's obj-c collision? Or is it C++ types that are
> typedefed differently for us, but conveniently named-mangled the same
> so they link?
>
> --Amanda
>
>
> On Wed, Mar 11, 2009 at 10:49 AM, Mark Mentovai <mmento...@google.com>
> wrote:
> > Avi Drissman wrote:
> >> 4. Figure out why system WebKit doesn't get along with our WebCore. I'm
> not
> >> sure where to start.
> >
> > Obj-C dynamic dispatch, I bet.
> >
> > Option 5: don't bring *any* of our own WebKit into the browser
> > process. In theory, we shouldn't need WebKit in our browser process
> > anyway - for multi-process mode. This approach won't solve the
> > single-process case.
> >
> > Option 6: finish porting WebKit the "right" way so that it's not
> > exposing any Obj-C that might conflict with interfaces that Cocoa
> > expects "system WebKit" to provide.
> >
> > Mark
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
