Tamas Cservenak opened MRESOLVER-321 and commented
As reported by users, under some conditions (MRESOLVER-316) resolver is able to spin itself into busy loop, without possibility to stop it (ie. by interrupting the thread of it).
Example report: #236
The reproducer (until MRESOLVER-316 is fixed) is present in PR above (the demo code and the diff for it).
While the PR proposes a code change, that is not covering all, as in case of MRESOLVER-316 bug, the endless loop happens in visitor bit (DependencyVisitor visiting DependencyNodes).
Solutiom: make collector but also visitor sense thread interruption.
Remote Links:
Backported to: 2.0.0-alpha-3
Tamas Cservenak opened MRESOLVER-321 and commented
As reported by users, under some conditions (MRESOLVER-316) resolver is able to spin itself into busy loop, without possibility to stop it (ie. by interrupting the thread of it).
Example report: #236
The reproducer (until MRESOLVER-316 is fixed) is present in PR above (the demo code and the diff for it).
While the PR proposes a code change, that is not covering all, as in case of MRESOLVER-316 bug, the endless loop happens in visitor bit (DependencyVisitor visiting DependencyNodes).
Solutiom: make collector but also visitor sense thread interruption.
Remote Links:
Backported to: 2.0.0-alpha-3