-
Notifications
You must be signed in to change notification settings - Fork 430
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BundleException: Unable to acquire the state change lock for the module: osgi.identity #3184
Comments
@IKnewOne Could you try to set
for instance,
|
"-DwatchParentProcess=false" didn't seem to fix it entirely, but it looks like the file isn't blocked anymore whenever i try to clean and reload java workspace via command or even when exiting the vscode. But the error rarely appears after a java workspace reload. At least from what i can tell Changing java settings, which forced the reload with the new settings in place, seem to make the vscode behave until reload, even with the java clean workspace command, but it still fails after closing the vscode. Overall, it kinda makes it better, but it's still manual fixing |
Are you sure the build is complete? Could you attach your log? - Enable Logging |
Here's a log with empty redhat.java first run with ample time to build, followed by vscode exit, followed by opening vscode a second time and a third time |
Duplicate of #3032 |
@snjeza This appears to be a regression in vscode-java 1.20.0. In previous versions, I had not noticed #3032, but as of vscode-java 1.20.0, the issue occurs 100% of the time for me when working on Gradle projects (given a few preconditions, see #3032 (comment) for more details). Currently I have downgraded to vscode-java 1.19.0 as a workaround, because I'm working on Gradle projects, and this issue is very annoying as it basically forces you to run |
@0dinD @IKnewOne Could you, please, test VS Code 1.22.0 ? |
@snjeza so far seems to work with no issues on reload/bad exit/etc. Lombok and warnings are not being nice for some reason, but i hope that's irrelevant to the current issue so this is probably a fixed issue now ( until, of course, it regresses again ) |
Exiting VSC leaves a java process that blocks workspaceStorage/redhat.java files leading to deadlock on the files, thus breaking any functionality until i terminate the process manually, delete the redhat.java folder and start vscode. Neither developer reload for the window, nor java clearnup works. The latter doesn't work due to the same lock on the files.
Environment
Steps To Reproduce
Cannot attach the project
In terms of logs, it's always the same first error of a deadlock appearing instead of proper project
firstlogmessage.txt
Current Result
The project doesn't load java and endlessly send messages of a deadlock of over 30000ms
Expected Result
Proper functionality
Additional Informations
The text was updated successfully, but these errors were encountered: