Merged
Conversation
此处按照周志明老师《深入理解JVM虚拟机》第三版第七章虚拟机类的加载机制P279页的描述，此处可能会有的问题如果`<clinit>()`方法中有耗时很长的操作，其他进程由于无法获得锁会进入阻塞队列中一直等待。而死锁的定义是**指两个或两个以上的进程在执行过程中，由于竞争资源或者由于彼此通信而造成的一种阻塞的现象，若无外力作用，它们都将无法推进下去。** 而这里如果只是耗时时间过长的话并不会进入死锁，而是长时间处于阻塞队列中，耗时操作执行完成后，其他进程还是会正常执行下去。 所以这里使用进程阻塞是否会更好呢？？
Owner
很赞很赞很赞的提交PR的格式！感谢老哥帮忙完善！爱你 |
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
2 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.
此处按照周志明老师《深入理解JVM虚拟机》第三版第七章虚拟机类的加载机制P279页的描述，此处可能会有的问题如果
<clinit>()方法中有耗时很长的操作，其他进程由于无法获得锁会进入阻塞队列中一直等待。而死锁的定义是指两个或两个以上的进程在执行过程中，由于竞争资源或者由于彼此通信而造成的一种阻塞的现象，若无外力作用，它们都将无法推进下去。 而这里如果只是耗时时间过长的话并不会进入死锁，而是长时间处于阻塞队列中，耗时操作执行完成后，其他进程还是会正常执行下去。所以这里使用进程阻塞是否会更好呢？？