Closed Bug 283300 Opened 20 years ago Closed 19 years ago

If gdk_threads_init is called then gtkmozembed hangs in some situations

Categories

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

All
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: mirko, Assigned: mpgritti)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; it-IT; rv:1.7.5) Gecko/20050110 Firefox/1.0 (Debian package 1.0+dfsg.1-2)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; it-IT; rv:1.7.5) Gecko/20050110 Firefox/1.0 (Debian package 1.0+dfsg.1-2)

The widget causes a deadlock in some situations after gdk_threads_init is called. 

Please refer to http://developer.gnome.org/doc/API/2.0/gdk/gdk-Threads.html for
details. The test code can be downloaded from 
http://mirko.lilik.it/ruby-gnome2/moztest-unlock.c.

I've written another test application
http://mirko.lilik.it/ruby-gnome2/moztest.c which does not call gdk_threads_init
and thad _does_ work.

NOTES: 
- Tried the mozilla-1.7.5 version and the Firefox-1.0 version from debian sarge
and gentoo. 
- GNOME 2.8.1. 
- pkg-config gtk+-2.0 --modversion = 2.4.14. 
- pkg-config glib-2.0 --modversion = 2.6.2. 
- pkg-config gthread-2.0 --modversion = 2.6.2.
- pkg-config mozilla-gtkmozembed --modversion = 1.7.5


Reproducible: Always

Steps to Reproduce:
1. compile the test-app with: gcc `pkg-config gthread-2.0 gtk+-2.0
mozilla-gtkmozembed --cflags --libs` -o moztest-thread moztest-unlock.c
2. run ./moztest-thread
3. go to http://www.hangs-if-not-found-dialog-opens.nowhere
3b. go to www.macromedia.com (or other flash sites)

Actual Results:  
hangs

Expected Results:  
error dialog or page displayed
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.