GNOME Bugzilla – Bug 585458
crash in gtk.RecentInfo.get_application_info()
Last modified: 2009-08-11 13:26:32 UTC
The following code crashes for me reproducible: ### import gtk recent = gtk.recent_manager_get_default() for info in recent.get_items(): last_application = info.last_application() application_info = info.get_application_info(last_application) ### With something like *** glibc detected *** python: double free or corruption (!prev): 0x00000000024c4e20 *** please see the attachment for the complete backtrace. I'm not sure which further information are needed, but I'm happy to provide any information to debug this further. Markus
Created attachment 136344 [details] terminal output
I cannot reproduce this. Can you try if the bug happens with the latest (2.15.1) version for you? Are all statements above necessary? E.g. can you remove get_application_info call and still get a crash?
Nevermind, actually I can reproduce. Tried this in interactive mode and error hapenned only after I quit the interpreter.
Fixed in development branch.
hi Paul, wow, you are fast, thanks for the fix. Is the development branch available somewhere to the public? - I would like to check if this fixes my initial problems. When can I expect the release of this fix, is there a pygtk roadmap somewhere? Thanks again, Markus
(In reply to comment #5) > Is the development branch available somewhere to the public? - I would like to > check if this fixes my initial problems. Sure, see http://git.gnome.org/cgit/. You want 'master' branch. > When can I expect the release of this fix, is there a pygtk roadmap somewhere? We are way too low on human resources to make any promises. Hopefully soon, but no guarantee.
Thanks for fixing this. Can you say in which version this will be fixed? (2, 15, 2), (2, 16, 1), something else? We want to use this function in Zeitgeist and will have to use a workaround for now (parsing the XML files instead of using PyGTK for it). If you can guarantee in which version number this will be fixed I can add a conditional check to only use the workaround in older PyGTK versions.
(In reply to comment #7) > Thanks for fixing this. > > Can you say in which version this will be fixed? (2, 15, 2), (2, 16, 1), > something else? It will be really soon into 2.16.0.