81395 - gtkmozembed crash in notebook mode after destroying 1 embed and focusing away from the parent window

Status: RESOLVED DUPLICATE of bug 79022

(Core Graveyard :: Embedding: GTK Widget, defect)

Description

[Maher Awamy]

Using SkipStone in tabbed mode and browsing as regularly, then destroying one of
the tabs and focusing away from the parent window in any form (opening a dialog,
moving the cursor away from the parent window, dropping a menu, etc..) causes a
crash with the attached backtrace.
To reproduce
start a new session,
open a new tab
close one tab
focus away or select a menu or open a dialog.
Crash occurs, reproducable always.

Comment 1

[Maher Awamy]

Attachment: gdb backtrace

Comment 2

[Maher Awamy]

More info on this:

I found out that when ever I called mozilla_history_init(GtkMozEmbed *embed)
function in tabbed mode which in no way I have a clue why would cause this i got
this crash immediately like described, the function gets the docshell, then
docshellhistory and then initlizes global history all in one function.. when I
changed it to a c++ class with Init and Destroy() functions where it keeps a
mWebBrowser variable adn gets the docshell from that addRefed i worked better
but I still get that crash every now and then, it disappears completely if I
just omit calling hte global history, I'm in no way clued to why this happens,
that funciton has worked with Embed and Mozilla for quite a while by now .. Dont
know Chris.. Any clues?

Comment 3

[Christopher Blizzard (:blizzard)]

Maybe you have a stale reference to a particular history object?

Comment 4

[Maher Awamy]

I dont think so, because now Destory() function is called each time embed is
destroyed to delete the reference to SkipHistory class.. or do you mean
something else? btw, I have one more note about the embedding widget - dettabing
the only tab (which used to work before) crashes with gtk_container_resize error
now, I can attach a sample and trace here but I thought I ask first if you want
a new bug filed with other reparenting behaviros :)

Comment 5

[Christopher Blizzard (:blizzard)]

I'll bet that's related to not being able to reparent properly.  Please don't
put it in this bug it just muddles things.  Is there a bug open on that general
problem yet?

Comment 6

[Maher Awamy]

Not that I have seen, I can file one once I dig more into it. Since it used to
work but with weird issues (like reording childrens in teh box and etc).. 

Comment 7

[Christopher Blizzard (:blizzard)]

*** This bug has been marked as a duplicate of 79022 ***