<div dir="ltr">Hello, I don't think this would happen for JDK 24 - JEP 491 removed the code that calls Blocker in Object.wait, which is exactly the goal of that JEP.<div><div><br></div><div>Note that virtual threads are still pinned when call stack goes into native, as native execution may pass address to stack variables that will be lost in context switches. In these cases, the traditional managed block happens again.</div></div><div><br class="gmail-Apple-interchange-newline">P.S. I personally think it is somewhat not responsible for JDK vendors to ask users to upstream a question for an older JDK release that might no longer apply on the latest release to a development-oriented mailing list.</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, Jul 1, 2025 at 9:47 PM Jianbin Chen <<a href="mailto:jianbin@apache.org">jianbin@apache.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="auto"><br></div>Hi Loom-dev Community,<div dir="auto"><br></div><div dir="auto">I have a question about platform thread creation triggered by calling future.get() within virtual threads, and I would like to ask the community for assistance. The detailed information can be found in this issue: <a href="https://github.com/adoptium/adoptium-support/issues/1319" target="_blank">https://github.com/adoptium/adoptium-support/issues/1319</a>. I hope to receive some help from the community regarding this matter. Thank you.</div><div dir="auto">Additionally, I'd like to know if this situation will still occur in JDK 24 and above?</div><div dir="auto"><br></div><div dir="auto">Best Regards.</div><div dir="auto">Jianbin Chen, github-id: funky-eyes</div><div dir="auto"><br><br><div dir="auto">Best Regards.<br>Jianbin Chen, github-id: funky-eyes </div></div></div>
</blockquote></div>