Dreamview no response after clicking the button

[WentaoWang-SH]

I found that sometimes Dreamview looks like it's stuck, with no response when clicking the button.
such as: when I click opening GPS, In dreamview , it looks like already opened. but actually, there is no data in the GNSS topic. the GPS module is not opened successfully.

then, if I ran the command ./script/gps.sh , it responded : gps.sh was already running.
then I run the following command:
./script/gps.sh stoped
./script/gps.sh
the GNSS topic can receive data successfully.

so using the scripts, I can successfully open the module, but with dreamview there is no response.

here is also a test:
before I restart the dreamview, the following picture is the screenshot.
after stop and start the dreamview, and refresh the webpage, and select the vehicle, the dreamview was still the following picture.

Platform: D-kit apollo 2.5 ROS.

so, anyone can help me, and give me a direction for this issue.
thank you very much!

[daohu527]

before I restart the dreamview, the following picture is the screenshot.

If you just restart the dreamview, it will not restart the modules. and when dreamview start again, it will sync the status of the module by websocket.

So I think you should first stop the module and wait a while then start again.

[WentaoWang-SH]

before I restart the dreamview, the following picture is the screenshot.

If you just restart the dreamview, it will not restart the modules. and when dreamview start again, it will sync the status of the module by websocket.

So I think you should first stop the module and wait a while the start again.

the problem is that I can't close the module, because the dreamview is stuck. when I click "Reset All" or close all modules manually, actually it doesn't work, the modules are still open.

[YuqiHuai]

@daohu527 Hi! I am wondering if this issue has been investigated further.

I have been running dreamview for a few hours in a loop following order: reset, start sim control, send routing, (waits for completion), stop sim control.

I noticed after a while dreamview frontend's adc part completely freezes, even if I refresh the display does not change. I can still control sim control and send routing requests.

This might be similar to the original poster’s problem, somehow resetting is breaking internal mechanism. How should I go about debugging this?

I do not see anything useful in dreamview's info logs.
From browser console I see "Received duplicate simulation_world"
Based on this my hypothesis is "void SimulationWorldService::Update()" is not being called for some reason.

[daohu527]

From browser console I see "Received duplicate simulation_world"

That means dreamview backend don't send messages or lag, I'm not sure what's wrong, need more info

[YuqiHuai]

@daohu527 I understand. How can I get more information?

I inserted AINFO << "CALLING SIM_WORD_SERVICE_.UPDATE. Timer ID: " << timer_->GetID(); at the first line of the function

apollo/modules/dreamview/backend/simulation_world/simulation_world_updater.cc

Lines 719 to 721 in 986fe47

	void SimulationWorldUpdater::OnTimer() {
	sim_world_service_.Update();

I have added log statement for timer before and after calling callback, before and after calling sim_world_service_.Update()
So I got logs in the following format:

W0726 22:20:25.295905   291 timer.cc:83] timer [2 ] executing callback.
W0726 22:20:25.295949   291 simulation_world_updater.cc:731] CALLING SIM_WORD_SERVICE_.UPDATE. Timer ID: 2
W0726 22:20:25.297428   291 simulation_world_updater.cc:733] CALLED SIM_WORD_SERVICE_.UPDATE. Timer ID: 2
W0726 22:20:25.299073   291 timer.cc:85] timer [2 ] executed callback.

After another 2 hours of running, I noticed the last pattern ended at

W0726 22:20:25.395844   290 timer.cc:83] timer [2 ] executing callback.
W0726 22:20:25.395884   290 simulation_world_updater.cc:731] CALLING SIM_WORD_SERVICE_.UPDATE. Timer ID: 2

which means the SimWorldService.Update() function did not return for some reason.

[daohu527]

Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.