Closed Bug 6300 Opened 25 years ago Closed 25 years ago

[PP] apprunner: Going thru menu items causes Assertion failure...

Categories

(Core :: XUL, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: sas, Assigned: saari)

References

Details

(Whiteboard: Have a fix for all but one of the assertions)

==================================================
Product:     Mozilla, Release M5
BuildID:     1999050422
Environment: Linux Redhat 5.2, 2.0.36 i586 unknown
Xserver:     Exceed 5.1.3.0 on NT 4.0

How to simulate:
1. Run mozilla-apprunner.sh
2. Click on the test.html displayed on the first page
3. Press "Back"
4. Goto "Tasks" menu item. Slowly go to each of the menu item.
5. Goto "Bookmarks" menu item. Again slowly goto each of the menu items.
6. You can see many assertions being printed on the debug output.

===========Debug output===========
Added page
file:////home/sas/download/package/res/samples/BrowserInitPage.html
to the rdf:history datasource
Got a handle to forward menu item
Setting forward menu item enabled
Obtained MenuItem Back
Setting Back menuitem to enabled
Document
file:////home/sas/download/package/res/samples/BrowserInitPage.html
loaded successfully
nsMenu::MenuConstruct called
nsMenu::MenuDestruct called
nsMenu::MenuConstruct called
nsMenu::MenuDestruct called
nsMenu::MenuConstruct called
nsMenu::MenuDestruct called
nsMenu::MenuConstruct called
nsMenu::MenuDestruct called

Gtk-CRITICAL **: file gtkcontainer.c: line 717
(gtk_container_remove): assertion `widget->parent == GTK_WIDGET
(container)' failed.

[*** Above message repeats 20 times...]

Gtk-CRITICAL **: file gtkcontainer.c: line 717
(gtk_container_remove): assertion `widget->parent == GTK_WIDGET
(container)' failed.

nsMenu::MenuConstruct called
nsMenu::MenuConstruct called
menu_item_activate_handler

[*** Above message repeats 25 times...]

Gtk-CRITICAL **: file gtkcontainer.c: line 717
(gtk_container_remove): assertion `widget->parent == GTK_WIDGET
===========
Further comment:

After the above incident, the browser stops responding to mouse.
Another issues to be noted alogn with this is that, the network was
bad when this was observed (every 5th ping packet loss).
After a long time it again responded.

I doubt there may be bugs in the recovery from
network packet losses *also*.
Assignee: don → karnaze
Component: Apprunner → Widget Set
Assignee: karnaze → hyatt
Reassigning to Hyatt and CCing Ramiro. There is very apprunner specific
widgetry.
Assignee: hyatt → saari
Reassigning to saari.
Target Milestone: M7
I know about the assertions, but I've never seen the mouse stop responding.
Summary: apprunner: Going thru menu items causes Assertion failure... → [PP] apprunner: Going thru menu items causes Assertion failure...
the code to fix this is partially checked in to the tree.  i'll add myself to
the cc list on this one
QA Contact: leger → phillip
Updating QA Contact.
Target Milestone: M7 → M8
Moving all Widget Set bugs, past and present, to new HTML Form Controls
component per request from karnaze.  Widget Set component will be retired
shortly.
moving to XP Toolkit/Widgets since these are not HTML form controls
Target Milestone: M8 → M9
Don't have time to deal with this for M8, pushing to M9
*** Bug 9278 has been marked as a duplicate of this bug. ***
Ok, I lied... I am looking at this, but I may or may not get permission for M8
Status: NEW → ASSIGNED
Whiteboard: Have a fix for all but one of the assertions
Target Milestone: M9 → M10
XPMenus sort of negate this. Anyway, I still have a fix that I'd like to checkin,
but I'm not doing it today... pushing to M10
Target Milestone: M10 → M13
Since this is for native GTK menus, and we're using XPMenus now, I'm pushing this
out past the dogfood "beta"
Blocks: 12670
Target Milestone: M13 → M14
dividing up phillips bugs, he no longer works here
Target Milestone: M14 → M20
Native widgets, yeah right
what should i do with this one, chris?
Kill it. If we ever resurrect native menus I'm sure I can fix it again.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
this was fixed when we turned on XP menus.
yup, no longer see those assertions.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.