Re: [Opensync-devel] python wrapper and plugin

[Chris F. <cd...@fo...>]

On Thu, Aug 02, 2012 at 08:24:33PM -0400, Chris Frey wrote:
> Thanks!  Mine is crashing in a different place, but it is related to
> osync_list_copy() / osync_list_free(), and according to my valgrind runs,
> I'm starting to wonder if somehow Python's malloc system is being used
> by opensync.  The errors I'm getting are pretty weird, and valgrind
> seems to have lost track of where the memory came from.
> 
> This is early results, so clarity may come later. :-)

This is just a status update, in case others are working on this too.

One discovery so far today.... I usually set G_SLICE to always-malloc
for debugging purposes, but this does not seem to work well with the
C Python API for some reason.  Memory accesses get really confused.

It would be good if I could find a way to split the python_module.c plugin
into its own process, I think, but unfortunately, it needs to call into
python in order to register the python scripts' plugins.  And this happens
before initialize.

I'm still sensing some odd memory behaviour with Python, but haven't
tracked it all down yet.

Removing all the _unrefs() from the opensync library python wrapper seems
to help a bit though. :-)

- Chris