Open frankbenoit opened 1 year ago
Please if Eclipse hangs, run jstack and attach generated thread dump here.
This doesn't show a deadlock. I guess the output is very specific, either too long lines or something SWT can't render fast enough.
The console output of the completed test does have 22000 log lines. In the beginning there are 3 lines that are very long with 31724 characters each. Here ArchUnit lists the class-path with all found jar files.
.. and "word wrap" button was pressed. (perhaps relevant)
.. and "word wrap" button was pressed. (perhaps relevant)
That is it. World wrap is not working well with lot of output.
Hm, for me it is fine now, I know how to workaround now. Perhaps this issue can be closed. But a hard lesson for everyone coming into the same situation.
VS Code solves this by showing the first 1000 chars, then a tag "Show more (21KB)". When pressing it, it shows raw text only and switches off enhanced capabilities for performance reasons.
So there is a potential logic bug ... When the console view is having word-wrap AND is initially not visible AND a first output with long lines is pushed, then it makes the IDE to freeze forever. If it is initially visible OR does not have word-wrap, it works well.
word wrap is disabled by default and also the buffer is very limited by default. If you change that you need to live with it or propose a performance improvement patch
Since 2023-06, and still with 2023-09 I experience a deadlock of the Eclipse IDE when I run a JUnit test on project level.
Steps to reproduces:
The status bar shows "Starting ...", the UI freezes and never comes back.
With "YourKit" I detected this potential dead lock, because this thread is locked for more than 10 seconds:
Now, when I open the "Console" view first, I can avoid the deadlock.