Upgraded librealsense, now getting error related to backend-v4l2.h and memory leak? #1142
Comments
|
I'd also add that now the process seems to completely overwhelm my CPU and make my computer unusable. Something seems quite wrong ... |
|
Can you see the same behavior when running a single camera? Can you see that using realsense-viewer? |
|
I get the same behavior with a single camera. It's hard to check with |
|
I’m running the most recent firmware, librealsense2 (Debian package) and realsense-ROS library (built from source):
Firmware:
D435 running firmware version 05.12.03.00
realsense-ros:
version 2.2.13
Librealsense:
librealsense2/bionic,now 2.33.1-0~realsense0.2079 amd64 [installed]
librealsense2-dbg/bionic,now 2.33.1-0~realsense0.2079 amd64 [installed]
librealsense2-dev/bionic,now 2.33.1-0~realsense0.2079 amd64 [installed]
librealsense2-dkms/bionic,now 1.3.13-0ubuntu1 all [installed]
librealsense2-gl/bionic,now 2.33.1-0~realsense0.2079 amd64 [installed,automatic]
librealsense2-gl-dbg/bionic 2.33.1-0~realsense0.2079 amd64
librealsense2-gl-dev/bionic 2.33.1-0~realsense0.2079 amd64
librealsense2-udev-rules/bionic,now 2.33.1-0~realsense0.2079 amd64 [installed,automatic]
librealsense2-utils/bionic,now 2.33.1-0~realsense0.2079 amd64 [installed]
ros-melodic-librealsense2/bionic 2.33.1-2bionic.20200309.152858 amd64
ros-melodic-librealsense2-dbgsym/bionic 2.33.1-2bionic.20200309.152858 amd64
On Mar 25, 2020, at 12:24 AM, doronhi <notifications@github.com> wrote:
Can you see the same behavior when running a single camera? Can you see that using realsense-viewer?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#1142 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA2CQOOWQ3IKS46JLUKTDD3RJGPRHANCNFSM4LSHWQ2Q>.
|
|
It's a kernel/librealsense2 issue that needs investigating. |
|
Unfortunately I only have the one computer, so it's hard for me to check other kernels... |
|
@ev-mp , this seems like a librealsense2/kernel issue. Any thoughts? |
|
I am also dealinbg with this same thing. I have done all the same things as stated above. |
|
Hello @poorboy44 @doronhi I figured something our on our end. SCRATCH THAT WE JUST LET IT RUN FOR A HOUR AND IT STARTED REPRODUCING THE SAME ERROR |
|
What is the firmware version?
…Sent from my iPhone
On Apr 6, 2020, at 12:37 PM, Mike Eichenberg <notifications@github.com> wrote:
Hello
I figured something our on our end.
We were using the same kernal version as you but the only thing different was my Intel d415 firmware was using Pre released firmware.
I simply put my firm back to a stable version and did not see the backend-v4l2.h error.
hope this helps
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#1142 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA2CQOKYQJHVQEYVYD63QG3RLIOOPANCNFSM4LSHWQ2Q>.
|
|
i am using 5.12.01 But we still are getting the same error. |
|
I haven’t...
…Sent from my iPhone
On Apr 6, 2020, at 1:19 PM, Mike Eichenberg <notifications@github.com> wrote:
i am using 5.12.01
But we still are getting the same error.
Have you been able to fix this issue on your side.
@poorboy44<https://github.com/poorboy44>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1142 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA2CQONWPESHNDRNN4OM2RLRLITNPANCNFSM4LSHWQ2Q>.
|
|
Is there anything we can do to get this to work. |
|
I still don't have a lead yet. Can anyone check if it appears with a librealsense application as well, such as realsense-viewer or rs-data-collect? I'm trying to establish if this is a ROS wrapper issue or a librealsense one. |
|
Are you not able to reproduce the issue with the latest librealsense/firmware/ROS wrapper?
…Sent from my iPhone
On Apr 7, 2020, at 9:01 AM, doronhi <notifications@github.com> wrote:
I still don't have a lead yet. Can anyone check if it appears with a librealsense application as well, such as realsense-viewer or rs-data-collect? I'm trying to establish if this is a ROS wrapper issue or a librealsense one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1142 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA2CQOMPSRKE4HXVC4H6WNTRLM56BANCNFSM4LSHWQ2Q>.
|
|
@doronhi I am working with @mikeNike9 on this project. We tested with librealsense-viewer and had the same issue occur. |
|
@doronhi |
|
Hi all, In order to assist you in the most efficient manner, we need more information about the issue. Along with that information, please share with us Intel.RealSense.Viewer logs and describe the exact scenario that leads to the problem. Thank you! |
|
Intel Celeron J1900 Output from realsense-viewer log: Output from rs_aligned_depth: These logs are from the first time I got on this morning to run both of these programs. In addition, I upgraded librealsense to 2.34.0 and am getting the same error with less frequency in realsense viewer, but still occurring. Also, another error: "ERROR [140456452417280] (types.h:307) get_device_time_ms() took too long (more than 2 mSecs) |
|
I upgraded to the latest librealsense debian packages, and seem to be unable to reproduce the issue so far. Here's what I have installed: |
|
Interestingly, the ROS logs indicate that it's still using |
|
@poorboy44 I was able to update all the debian packages and that seems to have fixed the v412.h backend error. We now have new errors that we will post in a new issue. Thanks! |
|
@haydenhager, Thank you for the provided details. Thank you! |
I upgraded librealsense to
2.33.1-0~realsense0.2079. I am running Ubuntu 18.04 with Linux kernel version5.3.0-42-generic.Now when I run the ROS integration, I get errors related to
backend-v4l2. Can you advise?The text was updated successfully, but these errors were encountered: