After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 370767 - Segmentation fault in gtkmozembed
Segmentation fault in gtkmozembed
Status: RESOLVED NOTGNOME
Product: gnome-python-extras
Classification: Deprecated
Component: gtkmozembed
2.14.x
Other Linux
: High critical
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-04 23:10 UTC by Matthew Barnes
Modified: 2006-12-24 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthew Barnes 2006-11-04 23:10:20 UTC
Forwarding this from a downstream bug report:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=205499

Verified using the gtkmozembed module in gnome-python-extras 2.14.2.

The following Python program causes a segmentation fault:

    import gtk
    import gtkmozembed

    class TinyGecko:
        def __init__(self):
            self.moz = gtkmozembed.MozEmbed()
            win = gtk.Window()
            win.add(self.moz)
            win.show_all()
            data = '<html><head><title>Hello</title></head><body>pygtk
dev</body></html>'
            self.moz.render_data(data, long(len(data)), 'file:///', 'text/html')

    if __name__ == '__main__':
        TinyGecko()
        gtk.main()
Comment 1 John Dennis 2006-11-17 00:46:10 UTC
Added some more debugging analysis in the original bug report

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=205499

hoping someone who knows this code better than I do might jump in.
Comment 2 John Dennis 2006-11-17 01:16:05 UTC
FWIW, the C test program TestGtkEmbed fails exactly the same way, thus the failure does not seem to have anything to do with the python binding. Anybody run the tests?
Comment 3 Gustavo Carneiro 2006-12-24 18:40:45 UTC
This bug is in mozilla.