yade-dev team mailing list archive

[Anton Gladky <1314736@xxxxxxxxxxxxxxxxxx>]

2014-05-07 19:47 GMT+02:00 Bruno Chareyre <1314736@xxxxxxxxxxxxxxxxxx>:
> It was my suggestion in #2 Anton. Define the number of threads explicitely for the collider (in your script):
> collider.ompThreads=1

Yes, I confirm that.

> It will switch to 1-thread variant of the sort. Could you please confirm that it avoids the crash?
> If so, I will just make the switch automatic, so nobody has to worry about that.

That would be fine!

Anton

-- 
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1314736

Title:
  Segfault possibly in new parallel collider

Status in Yet Another Dynamic Engine:
  New

Bug description:
  I have got segfault, which is probably due to a new parallel collider.
  It happened on my "local" version, which is not yet merged to the main
  branch [1] (with ENABLE_LIQCONTROL=ON option), but it is unlikely due
  to my changes.

  Before the crash I have got the following warning several times:
  ERROR /home/gladk/dem/yade/trunk/pkg/common/InsertionSortCollider.cpp:132 insertionSortParallel: parallel sort not guaranteed to succeed; in chunk 1 of 2, bound descending past half-chunk. Consider turning ompThreads=1 for thread safety.
  ....
  ....
  Segmentation fault

  I will try to provide the minimal script, which produces such
  segfault. Bruno, maybe you have an idea, where it crashes?

  [1] https://github.com/gladk/trunk

  Thanks

  
  Anton

To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/1314736/+subscriptions