yade-dev team mailing list archive

[Bruno Chareyre <1314736@xxxxxxxxxxxxxxxxxx>]

> if I set -j1, then there is not crash any more.

At least, it is consistent with the error message "Consider turning ompThreads=1 for thread safety".
I think you don't have to use -j1, setting collider.ompThreads=1 should be enough (the the other engines can still run parallel).

I guess you have a small number of particles or a very peculiar geometry, and also fast moving objects. Correct? In such case the parallel collider can fail in the sort phase. This situation is detected already (hence the error message).
The fix I can imagine is to turn collider.ompThreads=1 automatically instead of sending error messages.

Bruno

-- 
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