136368 - Selecting quit from the File menu causes a Gtk-CRITICAL assertion: main_loops != NULL

Status: RESOLVED WORKSFORME

(Core Graveyard :: Viewer App, defect)

Description

[Michael Sinz]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9+) Gecko/20020405
BuildID:    20020409

Selecting quit from the file menu causes the following assert:

Gtk-CRITICAL **: file gtkmain.c: line 582 (gtk_main_quit): assertion `main_loops
!= NULL' failed.


Reproducible: Sometimes
Steps to Reproduce:
1.Run Mozilla (browser)
2.View some pages
3.Select File->Quit

I have not noticed how to get this to happen.  It happened twice this morning
but when I try to make it happen it does not.

Actual Results:  Gtk-CRITICAL **: file gtkmain.c: line 582 (gtk_main_quit):
assertion `main_loops != NULL' failed.


Since I was trying to exit anyway, the net result was what I wanted :-)

Expected Results:  Exit cleanly

Trunk build from around 8AM EDT on April 9, 2002

The problem, if limited to the exit code, is of minimal concern.  However, this
may just be a symptom of a more important bug.

Comment 1

[John Levon]

Did you make sure to uninstall any previous Mozillas first ?
Can you still reproduce this problem ?

Comment 2

[Michael Sinz]

I have not seen it recently but I don't always have the window that started
Mozilla around at the point in time when it exits.

Someone else here at WorldGate has seen it happen but that was last week.

I will try to reproduce it again.

(And, yes, I fully delete the old tree and re-install using the tarball that
is built during the build/packager process)

Comment 3

[Michael Sinz]

I have been specifically looking to see if this has happened over the last week
and I have not seen it.  Could it be that some other change happened to fix
this?  Or maybe there was a race condition that does not get triggered any more?

I hate it when "problems" go away without knowing how/why/etc.

If I see this again I will add on to this bug at that time.

Comment 4

[Kai Lahmann (is there, where MNG is)]

doesn't sound like.

Comment 5

[Michael Sinz]

I have not noticed this problem since the few times during 0.9.9 timeframe.  It
seems something got fixed.