El mié, 09-07-2008 a las 17:08 -0700, Mitko Haralanov escribió:
On Wed, 09 Jul 2008 19:41:31 -0400
I guess it is possible for the locking to add overhead since the entire
gtk uses one master lock.
Also, are you sure that it's the locks? Have you been able to load all
2500 images before
On Tue, 08 Jul 2008 19:57:23 -0400
Felipe Reyes [EMAIL PROTECTED] wrote:
I added a test case that shows (at least on my system) my trouble.
somebody can give me a clue?
The issue is locking. Changing the code to this seems to have solved
the problem:
class FillListStore(threading.Thread):
El mié, 09-07-2008 a las 16:02 -0700, Mitko Haralanov escribió:
On Tue, 08 Jul 2008 19:57:23 -0400
Felipe Reyes [EMAIL PROTECTED] wrote:
I added a test case that shows (at least on my system) my trouble.
somebody can give me a clue?
The issue is locking. Changing the code to this
On Wed, 09 Jul 2008 19:41:31 -0400
Felipe Reyes [EMAIL PROTECTED] wrote:
Yes, with the locks everything works fine, but the locks added some
overhead (about 10 secons when loading 2500 pictures), I suppose that
this is normal, right?
I guess it is possible for the locking to add overhead
hi folks,
I'm writing a software that uses gtk.IconView to show images (my photo
collection, so there are over 1000 pictures), and I'm experimenting
random segfaults with gtk.IconView and I can not figure it out the
reason, please if somebody has some tip on how to debug this.
I added a test
