Page 1 of 1

Using -s and -h parameters crashes v-rep

Posted: 13 Feb 2018, 11:47
by lpitonakova
Hi,

I am trying to run a simulation in headless mode and start it automatically. This previously worked fine in V-REP 3.4., however, in 3.5., when I do e.g.

Code: Select all

./vrep -h -s ~.../scenes/e-puckDemo.ttt
V-Rep crashes immediately with

Code: Select all

...
Initializing the Bullet physics engine in plugin 'DynamicsBullet_2_78'...
Engine version: 2.78
Plugin version: 9
Initialization successful.
Error: signal 11:
0   libv_rep.dylib                      0x000000010c7ac4a1 _Z11_segHandleri + 33
1   libsystem_platform.dylib            0x00007fff5a1f1f5a _sigtramp + 26
2   ???                                 0x0000700000973990 0x0 + 123145312221584
3   liblua.5.1.dylib                    0x000000010d3cb595 luaD_callhook + 185
4   liblua.5.1.dylib                    0x000000010d3d43d2 luaV_execute + 215
5   liblua.5.1.dylib                    0x000000010d3cbc41 luaD_call + 98
6   liblua.5.1.dylib                    0x000000010d3cb344 luaD_rawrunprotected + 85
7   liblua.5.1.dylib                    0x000000010d3cbea5 luaD_pcall + 62
8   liblua.5.1.dylib                    0x000000010d3c81ec lua_pcall + 103
9   libv_rep.dylib                      0x000000010c738300 _ZN16CLuaScriptObject26_runThreadedChildScriptNowEv + 1552
QObject::~QObject: Timers cannot be stopped from another thread
QMutex: destroying locked mutex
This happens on both Mac and Linux.

Re: Using -s and -h parameters crashes v-rep

Posted: 13 Feb 2018, 12:11
by lpitonakova
Just tried to removing the -s parameter and instead writing a plugin that runs simStartSimulation() after the scene has loaded, with the same crash effect.

Re: Using -s and -h parameters crashes v-rep

Posted: 15 Feb 2018, 09:01
by coppelia
Hello,

yes, you are right, we must have broken something for release 3.5.0...
We'll look into this and should then provide a revision release.

Cheers

Re: Using -s and -h parameters crashes v-rep

Posted: 27 Feb 2018, 11:28
by coppelia
We found the problem. Thanks for mentioning it.

You can download correction libs. At some later point, we will release a new revision (V3.5.0 rev2+).

Cheers