Tjaster94 / pywebkitgtk

Automatically exported from code.google.com/p/pywebkitgtk
Other
0 stars 0 forks source link

Facebook causes segfault #23

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. run the attached file
2. click the button
3. log into facebook

once logged in, you will see the following printed to the console, when you
close the window it segfaults

john@nzjrs-laptop:~/Desktop$ python crash.py 
** Message: NP_Initialize
** Message: NP_Initialize succeeded
** Message: NP_Initialize
** Message: NP_Initialize succeeded
** Message: NP_Initialize
** Message: NP_Initialize succeeded
** Message: NP_Initialize
** Message: NP_Initialize succeeded
crash.py:22: Warning: invalid uninstantiatable type `(null)' in cast to
`GtkWidget'
  gtk.main()
Segmentation fault

What version of the product are you using? On what operating system?
Ubuntu Intrepid, Python 2.5.2, python-webkit 1.0.1, libwebkit 1.0.1, Gtk
2.14.4, PyGtk 2.13

Original issue reported on code.google.com by John.Stowers on 16 Jan 2009 at 12:42

Attachments:

GoogleCodeExporter commented 8 years ago
Problem seems to go away if you add the line

bv.get_settings().props.enable_plugins = False

(i.e. disable flash)

Original comment by John.Stowers on 22 Jan 2009 at 11:39

GoogleCodeExporter commented 8 years ago
John, I'm not getting that segfault with the latest upstream WebKit/gtk. 
Perhaps we
need a new upstream WebKitGtk release but afaik that's being looked at by a few
people already. I'll leave this bug open until we get a new release. Nothing 
can be
done from our (pywebkitgtk) end.

Thanks for filing the bug report. 

Original comment by jmalo...@gmail.com on 24 Jan 2009 at 9:25

GoogleCodeExporter commented 8 years ago
I can confirm that the segfault that I reported is no longer present when using
version 1.0.1-4+r40220 from https://launchpad.net/~webkit-team/+archive

Original comment by John.Stowers on 28 Jan 2009 at 11:07

GoogleCodeExporter commented 8 years ago
Closing - we have a new release now.

Original comment by jmalo...@gmail.com on 7 Mar 2009 at 2:46