After upgrading from 35.2.1 to 35.3.1, the running interface of the software is stuck

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

We use the ORIN NX module. With version 35.2.1, our software works as shown below.

But with version 35.3.1, the software stalls abnormally, as shown in the video below

We compare these two versions of the presentation, and it looks like the underlying software version is the same.

image
image1907×650 108 KB

We use the same set of hardware equipment, as well as the same set of software source code, but the L4T version is different, for testing.

How can I troubleshooting the problem? From the running situation of the program, the click switch function has finished running, but the interface refresh has some problems.

3

Hi,

Could you describe more details about the interface issue?
Do you mean something issue related to the UI?

Thanks.

4

Sorry for the late recovery, our program uses QT to do the UI interface. The UI refresh of version 35.2.1 is normal. Since the 35.3.1 UI refresh has been delayed, we’ve ensured that the QT version is consistent. Include other libraries with consistent versions.

5

Hi,

Could you share a reproducible source with us so we can check it further?
Please also help us to collect the status of the GPU usage for both cases.

$ sudo tegrastats

Thanks.

6

We found this problem when using QT’s OpenGL library to call GPU rendering. Do you have any good suggestions?

7

Hi,

It looks like the UI is blocked as the GPU resources are occupied.
Could you monitor the device to see if the GPU is fully utilized?

$ sudo tegrastats

Thanks.

8

Logging with latency:
out_abnormal.txt (39.5 KB)

Normal record
out_normal.txt (7.8 KB)

9

Hi,

From your tegrastats log:

r35.2.1

11-29-2024 15:21:48 RAM 8963/14486MB (lfb 10x4MB) SWAP 4/7243MB (cached 0MB) CPU [7%@1984,3%@1984,4%@1984,0%@1984,100%@1984,0%@1984,0%@1984,0%@1984] EMC_FREQ 1%@3199 GR3D_FREQ 28%@917 GR3D2_FREQ 28%@0 VIC_FREQ 115 APE 174 CV0@43.093C CPU@46.031C SOC2@42.156C SOC0@42.031C CV1@42.843C GPU@42.093C tj@46.031C SOC1@44.906C CV2@41.875C VDD_IN 8764mW/10415mW VDD_CPU_GPU_CV 2835mW/3916mW VDD_SOC 2596mW/2811mW

r35.3.1

11-29-2024 15:17:15 RAM 8996/15388MB (lfb 3x2MB) SWAP 24/7694MB (cached 0MB) CPU [5%@1984,4%@1984,2%@1984,100%@1984,5%@1984,1%@1984,4%@1984,4%@1984] EMC_FREQ 1%@3199 GR3D_FREQ 0%@917 GR3D2_FREQ 0%@0 VIC_FREQ 729 APE 174 CV0@42.281C CPU@46.343C iwlwifi@49C SOC2@42.437C SOC0@44.218C CV1@42.75C GPU@42.906C tj@46.343C SOC1@44.187C CV2@41.281C VDD_IN 9778mW/9629mW VDD_CPU_GPU_CV 2912mW/2811mW VDD_SOC 2515mW/2481mW

The VIC frequency of the r35.3.1 environment is much higher (729 vs. 115)
Is there any app using VPI VIC hardware in the background?

Thanks.

10

Could you please provide commands or tell me how to query apps using VPI hardware? We just deployed the same software program at present.

11

Hi,

Sorry that it is a typo.
It should be VIC instead of VPI.

VIC (Video Image Compositor ) is used for 2D image and video operations.
Like UI scaling, blending and rotation operations, and video post-processing.

Is there any related app running at the same time?
If not, could you share a reproducible source/steps so we can test it in our environment?

Thanks.

12

testOpenglApp.tar.gz (25.6 MB)
Execute the qttest1 file in the testOpenglApp directory.

qttest1.tar.gz (1.0 MB)
Here is the sample source package.

13

Hi,

Thanks for sharing the source.
To help us test this quickly, could you also share the command of setup and execute the qt app?

Thanks.

14

We use qtcreator to compile it.

At the same time, you can directly run the binary file to see the phenomenon.

15

Hi,

Would you mind sharing the commands/steps to reproduce this issue directly?
This will help us to give it a try quickly.

Thanks.

16

The steps of reproducing a phenomenon.

sudo apt-get install qtcreator -y
tar -xf testOpenglApp.tar.gz && cd testOpenglApp/
./qttest1

And then，As shown in the video，Use the mouse to repeatedly click the Normal Page and Opengl Widget buttons in the upper-left corner of the interface.
After a single click, the screen changes slowly without moving the mouse or keyboard.

17

Select the switch interface by tab switch + space. When switching back to the normal interface, do not move the mouse, or no longer press the tab key, and the screen will not switch

18

Thanks, will give it a try and update more info to you.

20

Hi,

Thanks for sharing the steps.
We do test it internally but are not able to reproduce this issue.

Please find the video below:

Would you mind reflashing your system with r35.3.1 to see if this can fix your issue?

Thanks.

21

Is it normal when the mouse does not move the mouse after clicking? Or use the keyboard tab key + space bar to switch, press the tab key once, and then press the space bar again, and keep the mouse still.

We’ve re-created flash several times. ORIN NX modules have also been replaced.

22

According to the video, you moved the mouse immediately after clicking the button. I hope you can test a click without moving the mouse.