[
https://issues.apache.org/jira/browse/LUCENE-9661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264339#comment-17264339
]
Uwe Schindler commented on LUCENE-9661:
---------------------------------------
Hi,
I checked the ECJ compiler settings, there's nothing detecting that.
If we would be able to enable this is ECJ, our checks with ECJ could detect
this problem.
I will dig further, unfortunately, InteliJ's compiler or code analyzer cannot
be executed from command line or Gradle, like ECJ can do.
> Another classloader deadlock?
> -----------------------------
>
> Key: LUCENE-9661
> URL: https://issues.apache.org/jira/browse/LUCENE-9661
> Project: Lucene - Core
> Issue Type: Bug
> Affects Versions: 8.0, master (9.0)
> Reporter: Michael McCandless
> Priority: Blocker
> Fix For: 8.x, master (9.0), 8.8
>
> Attachments: deadlock inspections.jpg, deadlock_test.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The {{java}} processes spawned by our Lucene nightly benchmarks sometimes
> randomly hang, apparently while loading classes across threads, under
> contention.
> I've opened [this {{luceneutil}} issue with some
> details|https://github.com/mikemccand/luceneutil/issues/89], but
> [~uschindler] suggested I open an issue here too since he has been seeing
> this in CI builds too.
> It is rare, maybe once a week in the nightly benchmarks (which spawn many
> {{java}} processes with many threads across 128 CPU cores). It is clearly a
> deadlock – when it strikes, the process hangs forever until I notice and
> {{kill -9}} it. I posted a coupled {{jstacks}} in the issue above.
> [~rcmuir] suggested using {{classcycle}} to maybe statically dig into
> possible deadlocks ... I have not tried that yet.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
