Committed fix for a potential problem with values being GCed too early

0 views

Skip to first unread message

Joao Cachopo

unread,

Jun 25, 2009, 5:13:24 PM6/25/09

to fenix-f...@googlegroups.com

Hello to all,

I've just committed a fix to the fenix-framework that solves a problem
that probably manifests itself very rarely but that it was there
nevertheless. (Luis and Paulo, I believe that this was the cause for
that strange behavior of the counter going backwards some months ago.)

The problem was that an older transaction could see values from the
future (changed in some later transaction) in some situations. It could
occur if after the change made by the later transaction, the object
changed was garbage-collected and then read by a later transaction
before the old transaction accessed it.

I believe that it is fixed now. So, even though this should be a rare
event, you should upgrade your version of the fenix-framework to avoid
inconsistent behaviors.