Closed HemaZ closed 4 years ago
martins-mozeiko
commented
4 years ago Crash on k::DataBuffer::CreateResource most likely means running out of GPU memory.
GeForce 920MX seems to have only 2GB of memory. That's probably not enough for Unity's HDRP rendering for simulation. It may run for very simple scenes (low res textures, simple meshes), but for environment simulator is using more memory is required. Using GPU with at least 8GB is recommended for Simulator.
HemaZ
commented
4 years ago ok, but can you update the docs and add minimum requirements or something.
EricBoiseLGSVL
commented
4 years ago 
lemketron
commented
4 years ago More specifically: https://www.lgsvlsimulator.com/docs/getting-started/#getting-started
True these are "recommended" but it's hard to say what the "minimum" requirements are as we do not have access to older generation GPUs, and GPU memory requirements vary based on other applications that may be running as well as the GPU requirements of the desired 3D environment being used in the simulator.
That said, I believe it's best to stick with a 10x0 series, with at LEAST 4GB of GPU memory to run JUST the simulator with a basic environment and nothing else running. You can check GPU memory usage with the nvidia-smi tool.
dr563105
commented
4 years ago I'm having the exact same issue from last night. I have 2 RTX 2080 Ti graphic cards of 11GB each and still the simulator crashes if a python script(ran from docker) also using GPU is already running. Only solution I have right now is to start simulator first and then run the script.
Also possible because HDD crashed today and had to do recovery. Docker service was affected. Had to reinstall docker. Fortunately, nvidia-docker and runtime container are ok. Using 2020.03 Simulator.
Can you please help?
Attaching player log. LGSVLplayer.log
martins-mozeiko
commented
4 years ago @dr563105 As your log shows same call stack on crash, please monitor GPU memory usage when running simulator. Check that it does not run out of memory. It maybe that you have some other software running that uses too much memory. nvtop is nice utility to use for monitoring memory on Nvidia GPU.
dr563105
commented
4 years ago Thanks @martins-mozeiko. You were right. Used nvidia-smi to monitor the GPU memory. When I ran the script, both GPU memories were full. Now I changed the script to use one and Sim the other. Running fine now.
marcusvinicius178
commented
3 years ago Hi @martins-mozeiko I had the same issue. My RAM is below:
lspci -v -s 01:00.0 Player.log
01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] (rev a1)
Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile]
Flags: bus master, fast devsel, latency 0, IRQ 133
Memory at a3000000 (32-bit, non-prefetchable) [size=16M]
Memory at 90000000 (64-bit, prefetchable) [size=256M]
Memory at a0000000 (64-bit, prefetchable) [size=32M]
I/O ports at 4000 [size=128]
Capabilities:
Also running: $nvidia-smi: NVIDIA-SMI 460.39 Driver Version: 460.39 CUDA Version: 11.2 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===============================+======================+======================| | 0 GeForce GTX 105... Off | 00000000:01:00.0 Off | N/A | | N/A 31C P8 N/A / N/A | 0MiB / 4042MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage
running: $lspci
lspci00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 05) 00:02.0 VGA compatible controller: Intel Corporation Device 591b (rev 04) 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) 00:15.0 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #0 (rev 31) 00:15.1 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #1 (rev 31) 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) 00:17.0 SATA controller: Intel Corporation HM170/QM170 Chipset SATA Controller [AHCI Mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 (rev f1) 00:1c.3 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #4 (rev f1) 00:1f.0 ISA bridge: Intel Corporation HM175 Chipset LPC/eSPI Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) 01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] (rev a1) 02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
My log file is attached below: Player.log I will appreciate if you support me to fix this core(dumped) error when I launch the lgsv simulator
$Found path: /opt/lgsvl/simulator Aborted (core dumped)
It starts opening and then fail unfortunately...
lemketron
commented
3 years ago My log file is attached below: Player.log I will appreciate if you support me to fix this core(dumped) error when I launch the lgsv simulator
@marcusvinicius178 I'm not sure why the simulator is aborting so early in the launch process. Looks like there may be some issue with Vulkan on your system.
It's possible you might have "mesa-vulkan-drivers" installed. If so, then you can remove that with sudo apt remove mesa-vulkan-drivers.
You can also try installing vulkan-tools (sudo apt install vulkan-tools). Then type vulkaninfo to verify that libvulkan is working, and then see if vkcube displays a window with a spinning 3D cube.
marcusvinicius178
commented
3 years ago Hi Steve thanks for replying I have restarted from scratch and now the simulator is working 😄.
Em dom, 7 de fev de 2021 17:22, Steve Lemke notifications@github.com escreveu:
My log file is attached below: Player.log https://github.com/lgsvl/simulator/files/5938327/Player.log I will appreciate if you support me to fix this core(dumped) error when I launch the lgsv simulator
@marcusvinicius178 https://github.com/marcusvinicius178 I'm not sure why the simulator is aborting so early in the launch process. Looks like there may be some issue with Vulkan on your system.
It's possible you might have "mesa-vulkan-drivers" installed. If so, then you can remove that with sudo apt remove mesa-vulkan-drivers.
You can also try installing vulkan-tools (sudo apt install vulkan-tools). Then type vulkaninfo to verify that libvulkan is working, and then see if vkcube displays a window with a spinning 3D cube.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/lgsvl/simulator/issues/827#issuecomment-774741683, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKOL2BRF6VQHK2MOAM2ELGLS53R5TANCNFSM4OJVYRTA .
spicker23
commented
3 years ago My log file is attached below: Player.log I will appreciate if you support me to fix this core(dumped) error when I launch the lgsv simulator
@marcusvinicius178 I'm not sure why the simulator is aborting so early in the launch process. Looks like there may be some issue with Vulkan on your system.
It's possible you might have "mesa-vulkan-drivers" installed. If so, then you can remove that with
sudo apt remove mesa-vulkan-drivers.You can also try installing vulkan-tools (
sudo apt install vulkan-tools). Then typevulkaninfoto verify that libvulkan is working, and then see ifvkcubedisplays a window with a spinning 3D cube.
I faced the same problem. Do I need to remove it for ade or for whole system?
EricBoiseLGSVL
commented
3 years ago The whole system
marcusvinicius178
commented
3 years ago Hi there are 2 simulators. One simulador inside ade that the creators of Autoware used to make easy their life to test demos and packages, etc.this simulator works with rviz2 using ros2 native bridge and there are not ROS- REAL car actuator messages conversion. To use this imternal simulador inside Ade (the one suitable to run their demos on website) then you have 2 steps: 1- modify your .aderc file and remove the line that says something about "Nvidia drivers = True" remove this line and source .aderc file before enter the image. 2- sudo apt-get remove mesa-vulkan-drivers
The issue here is that ALWAYS when you exit the Virtual machine (Ade image) you will need to repeat the second command above and remove the drivers again. Because when you start the image the drivers are there again and you need to remove.
And also a simulator outside ade ( that you must download from Lg website). This external simulator is on your host system and works with rviz2 using ros2 bridge on vehicles configuration. For the simulador outside ade there are just one step: 1- sudo apt-get remove mesa-vulkan-drivers
Later is just configure the ros2-lgsvl-bridge to use with rviz2 and modify the rviz2 topics on vehicles urdf in LG simulator or set them properly in rviz2 based on LG vehicles urdf because the tutorials of Autoware Auto writes them for the internal simulator, that has different topics for lidar, sensors, etc
I hope it works.
Em sáb, 27 de mar de 2021 10:26, spicker23 @.***> escreveu:
My log file is attached below: Player.log https://github.com/lgsvl/simulator/files/5938327/Player.log I will appreciate if you support me to fix this core(dumped) error when I launch the lgsv simulator
@marcusvinicius178 https://github.com/marcusvinicius178 I'm not sure why the simulator is aborting so early in the launch process. Looks like there may be some issue with Vulkan on your system.
It's possible you might have "mesa-vulkan-drivers" installed. If so, then you can remove that with sudo apt remove mesa-vulkan-drivers.
You can also try installing vulkan-tools (sudo apt install vulkan-tools). Then type vulkaninfo to verify that libvulkan is working, and then see if vkcube displays a window with a spinning 3D cube.
I faced the same problem. Do I need to remove it for ade or for whole system?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/lgsvl/simulator/issues/827#issuecomment-808732753, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKOL2BSILVM2I5EL74SXLTLTFXMH3ANCNFSM4OJVYRTA .
Hello lgsvl, when I try to run the simulator on my machine which runs ubuntu 18.04 CPU: Intel i5-7200U (4) @ 3.100GHz GPU: NVIDIA GeForce 920MX GPU: Intel Integrated Graphics Memory: 11882MiB I've the latest nvidia drivers and vulkan I can open http://localhost:8080 but when I try to run any simulation it shutdowns.
here is my log file