Ok, one more fix is in f22afe466ee5 commit.
Thanks. Chiara for pointing this out and providing a fix.
Anton
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/803774
Title:
Saving, loading simul
On 16 Jul 2012, at 02:00, Chareyre wrote:
> This fix is correct I think.
> If I guess correctly (I didn't check the code), the problem is that calling
> erase(i) on an interaction is not erasing immediatly. Instead it sends a
> message to the collider to erase "i" at next step. If you save, the ne
This fix is correct I think.
If I guess correctly (I didn't check the code), the problem is that calling
erase(i) on an interaction is not erasing immediatly. Instead it sends a
message to the collider to erase "i" at next step. If you save, the next
step never comes and junk interactions are saved
Well, if it fixes your problem, at least prevents a crash, I am ok to
commit it. I don't see any regressions here.
Please, let me know.
Anton
2012/7/15 Chiara Modenese :
> I found one solution but I think is a temporary fix. The problem is that
> somehow interactions are not deleted properly. B
I found one solution but I think is a temporary fix. The problem is that
somehow interactions are not deleted properly. Below is a modified
version of postLoad__calledFromScene - I am checking whether both bodies
in contact actually exist before the interaction is inserted, otherwise
return - but i
Running one additional step without erasing may avoid the problem, but it
still needs a fix.
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/803774
Title:
Saving, loading simulation with erased
On 15 Jul 2012, at 11:20, Chareyre wrote:
> postLoad is trying to insert interactions with deleted body.
> Did you erase just before saving?
Exactly! How to overcome the problem? I think that Anton's fix was/is not
sufficient to solve it...
Chiara
>
> --
> You received this bug notification be
postLoad is trying to insert interactions with deleted body.
Did you erase just before saving?
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/803774
Title:
Saving, loading simulation with eras
Hi all,
Unfortunately I am still affected by this bug. I cannot provide a simple
script but below is what I obtained in debug mode. Could you please
help? Thanks very much. Chiara
yade --debug
Welcome to Yade unknown (debug build)
TCP python prompt on localhost:9001,
OK, I had to do a clean scons but now it works fine so I confirm the fix was
appropriate. Thanks, Anton.
Chiara
On 15 Jun 2012, at 10:37, Anton Gladky wrote:
> 2012/6/15 Chiara Modenese :
>> OK, I see, thank you very much. Is the body deleted then? The length of
>> the container is still the sam
There is no need to post a script. You can (I can, at least) reproduce
the bug just by following instructions that were given below when the
bug was open. I think it is quite essential that we fix this as removing
bodies is a common operation. Can you please try to reproduce the bug
too, Anton (or
2012/6/15 Chiara Modenese :
> OK, I see, thank you very much. Is the body deleted then? The length of
> the container is still the same when I delete something, even after the
> fix.
That is right. By this way we are trying to escape memory leaks, using
for newly created bodies the "places" of pre
OK, I see, thank you very much. Is the body deleted then? The length of
the container is still the same when I delete something, even after the
fix. Before sending you the script, do you think it makes any difference
if I rerun the test with the new compilation? It will take a bit of time
for me if
Hi Chiara,
the fix is here [1]. It checks, whether the body exist before
clearing its intrs-container.
If you are still affected by this bug, please, send a short
script, reproducing the problem
Thanks
Anton
[1]
https://github.com/yade/trunk/commit/ce52daf69cc7b0d804703a0877ec68fafae8
201
Hi Anton,
I am currently affected by this bug. I am using an older release (but
not too old) andI updated the code following your fix in r2880. The bug
still occurs though but I have have not rerun the test. I reload the old
test using the code I recompiled after the change, I remove the bodies I
Hopefully fixed in r2880.
Please, check it. If the problem still appears, do not hesitate to reopen a bug.
** Changed in: yade
Status: New => Fix Released
** Changed in: yade
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yade
developer
** Branch linked: lp:yade
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/803774
Title:
Saving, loading simulation with erased bodies crash.
Status in Yet Another Dynamic Engine:
New
Bug de
For futur readers, including myself: it seems a "if (p)" before a "p->"
would help...
#7 0x7ffcc32a6941 in *__GI___assert_fail (assertion=0x7ffcbb0eff24 "px !=
0", file=, line=418, function=0x7ffcbb113240 "T*
boost::shared_ptr< >::operator->() const [with T =
Body]") at assert.c:81
#8 0x
** Attachment added: "debug-mode.txt"
https://bugs.launchpad.net/bugs/803774/+attachment/2185139/+files/debug-mode.txt
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/803774
Title:
Saving,
19 matches
Mail list logo
