[Bug 1246516] Re: Memory from slice allocator passed to PyObject_Free

2014-03-10 Thread Launchpad Bug Tracker
[Expired for pygobject (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pygobject (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in Ubuntu.

[Bug 1246516] Re: Memory from slice allocator passed to PyObject_Free

2014-01-09 Thread Martin Pitt
Ping? ** Changed in: pygobject (Ubuntu) Assignee: Martin Pitt (pitti) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1246516 Title: Memory from slice

[Bug 1246516] Re: Memory from slice allocator passed to PyObject_Free

2013-11-04 Thread Martin Pitt
Can you please give me some runnable code which reproduces this bug? I wrote a simple Gtk.Application test with HANDLES_OPEN which works fine. ** Attachment added: Gtk.Application test (works)

[Bug 1246516] Re: Memory from slice allocator passed to PyObject_Free

2013-10-31 Thread Ryan Lortie
This is not the same as the error we were seeing before: that error was an invalid read on memory that was just before a piece of memory that was allocated through the slice allocator. There is no gslice in this trace... -- You received this bug notification because you are a member of Ubuntu

[Bug 1246516] Re: Memory from slice allocator passed to PyObject_Free

2013-10-30 Thread Robert Bruce Park
This cropped up when I changed the following code: Gtk.Application.__init__(self, application_id='foo', flags=Gio.ApplicationFlags.HANDLES_COMMAND_LINE) To this: Gtk.Application.__init__(self, application_id='foo', flags=Gio.ApplicationFlags.HANDLES_OPEN) Not sure if that helps you track it