It would be nice to track down the source of the null NativeViewId. I bet that corresponds to a real bug. -Darin
On Fri, Mar 20, 2009 at 9:36 AM, Adam Langley <[email protected]> wrote: > > On Fri, Mar 20, 2009 at 8:11 AM, Avi Drissman <[email protected]> wrote: > > http://codereview.chromium.org/47002 > > http://crbug.com/9060 > > There's several parts here: > * Why is the renderer asking questions about a NULL NativeViewId? > * Why does that result in a NULL pointer in the browser? > > I don't know the answer to the first. It's probably some assumption in > WebKit which assumes that it has a valid window at all times and we > break that with multiprocess. However, it seems to be harmless. > > As for the second: we currently take pointers, raw from the renderer. > This is just a hack. At some point, we need to make NativeViewIds be > something else and have a proper translation layer. But we don't yet. > > > > AGL > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
