fix: Fix front-end startup stuck#96
Merged
max-lvs merged 1 commit intolinuxdeepin:masterfrom Jan 19, 2024
Merged
Conversation
When the disk manager starts, it will send an quit message to the background service, then start a new background service, and wait for the new background service to start before displaying the main interface. In the extreme case, when the old service has not exited and the new service has not been started, the front end detects the existence of the service, then displays the main interface and sends a request to the old service. Since the old service may have exited during the execution of the request, the front end cannot receive the updateDeviceInfo signal and remains in the initialization interface. The solution is that the front end needs to determine the PID of the service process when waiting for the new background service to start to ensure that the new service is running. Log: fix front-end startup stuck Bug: https://pms.uniontech.com/bug-view-239747.html
wangrong1069
force-pushed
the
startup-stuck
branch
from
0ee8eb5 to
b8d85f5
Compare
|
TAG Bot TAG: 1.3.32 |
max-lvs
approved these changes
Jan 19, 2024
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: max-lvs, wangrong1069 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
This was referenced Jan 19, 2024
Open
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the disk manager starts, it will send an quit message to the background service, then start a new background service, and wait for the new background service to start before displaying the main interface.
In the extreme case, when the old service has not exited and the new service has not been started, the front end detects the existence of the service, then displays the main interface and sends a request to the old service. Since the old service may have exited during the execution of the request, the front end cannot receive the updateDeviceInfo signal and remains in the initialization interface.
The solution is that the front end needs to determine the PID of the service process when waiting for the new background service to start to ensure that the new service is running.
Log: fix front-end startup stuck
Bug: https://pms.uniontech.com/bug-view-239747.html