Good morning,
we have recently implemented a worker that listens and reacts to database
events. It is written in python and uses the most recent python driver (1.4.1)
together with the latest firebird server (2.5.3). However, the following three
exceptions are catched regularily even if there
Good morning,
as written yesterday we have recently implemented a way to react on database
events in our python based program. But we are facing several outages with that
implementation. First we encountered at least three errors when invoking
event_conduit(events), namely:
* Error
made it visible. So fixing the circular reference with weakref.proxy
will probably not fix the problem. I'm working on proper fix, but it's hard to
test. Can you help me with testing if I'll create a patch?
best regards
Pavel Cisar
IBPhoenix
Dne 7.11.2014 v 08:56 Dominik Psenner dominik.psen
@yahoogroups.com
Betreff: Re: AW: [firebird-python] Memory leak when using events
Hi,
Well, the script is nice but I can't use it without the database it uses :)
best regards
Pavel Cisar
IBPhoenix
Dne 7.11.2014 v 12:19 Dominik Psenner dominik.psen...@topcontrol.it
[firebird-python] napsal(a):
Hi
and report here.
best regards
Pavel Cisar
IBPhoenix
Dne 7.11.2014 v 12:43 Dominik Psenner dominik.psen...@topcontrol.it
[firebird-python] napsal(a):
Apologies, I should have explained that better. :-) The good thing (or bad?)
is, that the database can be any firebird database. It must not even
Ah, you were faster than I could write. Sorry for me being so persistent.
Unfortunately I am unable to post a file in the bug tracker now that the issue
is resolved, therefore I write you here.
The good thing is, 1.4.3 improved the situation. One cyclic reference has gone
away but there’s
I refreshed the package and it looks like the memory leak is almost gone. I can
observe that the number of EventBlock’s left in memory are equal to the count
of errors raised with the invoke of begin() (namely one of: unknown ISC error
0, error reading from connection, error writing to
*hm* .. not really.. then an AttributeError pops up:
2014-11-14 15:15:08.498000 50/51 (1|50:51|3|0)
event_conduit(['TC_IMPORT_QUEUE_UPDATED'])Exception in thread Thread-6:
Traceback (most recent call last):
File C:\Python27\lib\threading.py, line 810, in __bootstrap_inner
self.run()
File
waiting for events:)
best regards
Pavel
Dne 14.11.2014 v 14:08 Dominik Psenner dominik.psen...@topcontrol.it
[firebird-python] napsal(a):
I refreshed the package and it looks like the memory leak is almost gone. I
can observe that the number of EventBlock’s left in memory are equal to the
count
