Hi Justin, unfortunately, this is expected. libavg doesn't expect to be called from multiple python threads. Changing this involves some work, since all entry points into the library would have to be made thread-safe. Performance-wise, it wouldn't really help much either, since internally, libavg would just have to serialize everything anyway...
That said, it would be nice to have, since there are non-performance reasons for using multiple threads like avoiding polling - patches welcome. Sorry, Uli PS: Please don't start new threads by replying to an old one and changing the subject. On mail readers that sort by threads, this leads to misleading mail sort orders, since the thread id stays the same. Justin Maynard wrote: > Gday > > I've got some code that I've been working on for some time that builds my AVG > nodes from a data base. It's been working fine when run from the main thread. > > I just started trying to run the same code from another thread and I get a > segmentation fault when I try to add a image node. eg > > imageNode = "<image id=\"Modern_Photo_" + str(record[1]) + "\" x=\"" + > str(imageX) + "\" y=\"118\" href=\"" + filename +"\"/>" > ModernImageDiv.appendChild(Player.createNode(imageNode)) > > I'm guessing that this is because some other component that libAVG relies on > is not thread safe ?? > > Please let me know what information I can provide to help solve this problem. -- Ulrich von Zadow | +49-172-7872715 Jabber: [EMAIL PROTECTED] Skype: uzadow _______________________________________________ libavg-users mailing list [email protected] https://mail.datenhain.de/mailman/listinfo/libavg-users
