"Segmentation fault (core dumped)" error when "DomainLimiter" is added

Bug #1723454 reported by Giovanni Lorenzon on 2017-10-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Yade
Undecided
Unassigned

Bug Description

The simulation crashes each time the "DomainLimiter" is added to the Engine list.
Simulation is run with Yade 2017.01a on Ubuntu 17.04 x64 and properly works if the reported engine is not inserted, whilst returns the error:

"Segmentation fault (core dumped)"

after ~16k iterations when DomainLimiter is added.

Giovanni Lorenzon (gioloren) wrote :
Anton Gladky (gladky-anton) wrote :
Download full text (4.8 KiB)

Thanks for bug report. Backtrace is here:

==============
#0 0x0000557b10ddd180 in ()
#1 0x00007fac49e31cf9 in boost::python::converter::shared_ptr_deleter::operator()(void const*) () at /usr/lib/x86_64-linux-gnu/libboost_python-py27.so.1.62.0
#2 0x00007fac4bbb951a in boost::detail::sp_counted_base::release() (this=0x557b134a25c0) at /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:146
#3 0x00007fac4bbb9af5 in boost::detail::sp_counted_base::release() (this=<optimized out>) at /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:144
#4 0x00007fac4bbb9af5 in boost::detail::shared_count::~shared_count() (this=<optimized out>, __in_chrg=<optimized out>) at /usr/include/boost/smart_ptr/detail/shared_count.hpp:473
#5 0x00007fac4bbb9af5 in boost::shared_ptr<Body>::~shared_ptr() (this=<optimized out>, __in_chrg=<optimized out>) at /usr/include/boost/smart_ptr/shared_ptr.hpp:336
#6 0x00007fac4bbb9af5 in boost::shared_ptr<Body>::reset() (this=0x557b1356d900) at /usr/include/boost/smart_ptr/shared_ptr.hpp:667
#7 0x00007fac4bbb9af5 in BodyContainer::erase(int, bool) (this=0x557b11b86410, id=<optimized out>, eraseClumpMembers=eraseClumpMembers@entry=false) at ./core/BodyContainer.cpp:61
#8 0x00007fac4c0b17ce in DomainLimiter::action() (this=0x557b13686ba0) at ./pkg/dem/DomainLimiter.cpp:27
#9 0x00007fac4bc55cb2 in Scene::moveToNextTimeStep() (this=this@entry=0x557b11aa97b0) at ./core/Scene.cpp:88
#10 0x00007fac4bc58a63 in SimulationFlow::singleAction() (this=0x557b119961f0) at ./core/SimulationFlow.cpp:24
#11 0x00007fac4bc5c58f in ThreadWorker::callSingleAction() (this=0x557b119961f0) at ./core/ThreadWorker.cpp:71
#12 0x00007fac4bc59707 in ThreadRunner::call() (this=this@entry=0x557b11b887e0) at ./core/ThreadRunner.cpp:52
#13 0x00007fac4bc599e0 in ThreadRunner::run() (this=0x557b11b887e0) at ./core/ThreadRunner.cpp:26
#14 0x00007fac4bc5bb42 in boost::function0<void>::operator()() const (this=<optimized out>) at /usr/include/boost/function/function_template.hpp:770
#15 0x00007fac4bc5bb42 in boost::detail::thread_data<boost::function0<void> >::run() (this=<optimized out>) at /usr/include/boost/thread/detail/thread.hpp:116
#16 0x00007fac48ebbf96 in () at /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.62.0
#17 0x00007fac4eb72494 in start_thread (arg=0x7fac01d84700) at pthread_create.c:333
#18 0x00007fac4df91abf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97

==============
Full relevant backtrace:

#7 0x00007fac4bbb9af5 in BodyContainer::erase(int, bool) (this=0x557b11b86410, id=<optimized out>, eraseClumpMembers=eraseClumpMembers@entry=false) at ./core/BodyContainer.cpp:61
        b = @0x557b1356d900: {
          px = 0x0,
          pn = { ...

Read more...

Bruno Chareyre (bruno-chareyre) wrote :

No luck with the nullptr assumption. It segfaults on regular bodies.
I am unable to figure out what the problem is.
It is also not very reproducible, playing with the inspector can make the script pass the segfault point...
Bruno
___
code:
cerr<<"BodyContainer::erase -> reset: "<<id<<" "<<(bool) body[id]<<endl;
body[id].reset();

runtime:
BodyContainer::erase -> reset: 1070 1
Segmentation fault

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers