Note: There are a few cases of duplicates in user autocompletion which are being worked on.

seamonkey crashed Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged



3 months ago
3 months ago


(Reporter: iii_iii, Unassigned)


SeaMonkey 2.51 Branch

Firefox Tracking Flags

(Not tracked)




3 months ago
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170317000000

Steps to reproduce:

I visited this website:

And tried to do a search for nearby events by putting something in the zipcode box.

Actual results:

WARNING: file /home/seamonkey/comm-aurora/mozilla/ipc/chromium/src/base
It crashed as soon as I began typing in the box. A dialog box came up saying it could not save a crash report. The message below appeared in the xterm from which I launched Seamonkey.

/, line 216
ExceptionHandler::GenerateDump cloned child 2610
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
prompt:~> Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

Expected results:

A search. I will add some more detail in a comment. I don't want this to crash.

The version of Seamonkey is  seamonkey --version
Mozilla SeaMonkey 2.51a2 on 64 bit linux.

Comment 1

3 months ago
I went to this sub page from the menu.

This SM was built by me.

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0 SeaMonkey/2.51a2
Build identifier: 20170408215647

Shortly I will test in safe mode...

Comment 2

3 months ago
Did not happen in safe mode.

Comment 3

3 months ago
It did not happen with a new profile.

It happened with the default profile but with addons disabled, except for DOM inspector and Seamonkey Debug QA.

It did not happen with all addons including DOM inspector, and SM Debug QA.

Now I cannot recreate it with all addons back on. I don't understand. It maybe to do with scrolling down before the map has loaded.
You need to log in before you can comment on or make changes to this bug.