I'm trying to find a simple and reliable reproduction case
for this bug. i've seen it myself on a few occasions. The
short (and wholy unsatisfactory) solution is to reinstall
LEAP.
I suspect some sort of relation file corruption going on.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When a corruption occurs, it sticks, so there is further
backing to the theory of a corrupted relation. However,
there seems to be, in a heavily debugged version of LEAP, an
indication that the relation is ok, but the memory structure
is suspect. investigations continue...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=7704
I'm trying to find a simple and reliable reproduction case
for this bug. i've seen it myself on a few occasions. The
short (and wholy unsatisfactory) solution is to reinstall
LEAP.
I suspect some sort of relation file corruption going on.
Logged In: YES
user_id=7704
When a corruption occurs, it sticks, so there is further
backing to the theory of a corrupted relation. However,
there seems to be, in a heavily debugged version of LEAP, an
indication that the relation is ok, but the memory structure
is suspect. investigations continue...
Logged In: YES
user_id=7704
debug output attached.
Logged In: YES
user_id=7704
debug output attached.
Logged In: YES
user_id=7704
Fixed in 1.2.6.1!