"gzserver" received signal SIGSEGV, Segmentation fault
Thread 198 "gzserver" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f933bbfe700 (LWP 25829)] 0x00007f95b7a81b74 in std::__atomic_base<bool>::load ( __m=std::memory_order_seq_cst, this=0x7f951c045d90) at /usr/include/c++/7/bits/atomic_base.h:396 396 return __atomic_load_n(&_M_i, __m); (gdb) bt
0 0x00007f95b7a81b74 in std::__atomic_base<bool>::load(std::memory_order) const (__m=std::memory_order_seq_cst, this=0x7f951c045d90)
at /usr/include/c++/7/bits/atomic_base.h:396
1 0x00007f95b7a81b74 in std::atomic<bool>::operator bool() const (this=0x7f951c045d90) at /usr/include/c++/7/atomic:86
2 0x00007f95b7a81b74 in gazebo::event::EventT<void (gazebo::common::updateinfo="" const&)>::signal<gazebo::common::updateinfo="">(gazebo::common::UpdateInfo const&) (_p=..., this=<optimized out="">)
at /home/***/gazebo-9.0.0/gazebo/common/Event.hh:291
3 0x00007f95b7a81b74 in gazebo::event::EventT<void (gazebo::common::updateinfo="" const&)>::operator()<gazebo::common::updateinfo="">(gazebo::common::UpdateInfo const&) (_p=..., this=<optimized out="">)
at /home/***/gazebo-9.0.0/gazebo/common/Event.hh:128
4 0x00007f95b7a81b74 in gazebo::physics::World::Update() (this=this@entry=0x55fc0b613190) at /home/*/gazebo-9.0.0/gazebo/physics/World.cc:767
5 0x00007f95b7a8cc6b in gazebo::physics::World::Step() (this=this@entry=0x55fc0b613190) at /home/*/gazebo-9.0.0/gazebo/physics/World.cc:696
6 0x00007f95b7a8d11d in gazebo::physics::World::RunLoop() (this=0x55fc0b613190) at /home/*/gazebo-9.0.0/gazebo/physics/World.cc:505
7 0x00007f95b89686df in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
8 0x00007f95b7da96db in start_thread (arg=0x7f933bbfe700)
at pthread_create.c:463
9 0x00007f95b83c371f in clone ()
---Type <return> to continue, or q <return> to quit--- at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Why?
Hello,
can you provide more details ?
Is this happening when you launch ... ? - A demo (which one) - your own world - your own plugin/code
This trace is not enough to understand what is going on.
Hi,
I've only downloaded the GitHub's project
https://github.com/PierreExeter/jaco-gym
installed the several packages, and evoked
roslaunch kinova_gazebo robot_launch_render.launch kinova_robotType:=j2n6s300
and
python3 scripts/1_train_ppo2.py
. After the evoking, gzserver makes the "segmentation fault" sporadically.
I'm using Ubuntu18.04, ROS melodic, Python 3.6.9, gym-0.18.0 and gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0.
It seems to me that stack destruction is occurring.
Kazu