Jörg Kubitz

workaround: 1. show all threads. 2. Deselect a single thread 3. Merge selected threads. 4. Add the deselected thread again. => all merged

I can see it on every sampling. For example you can download this, and concentrate on the "main" thread: https://bugs.eclipse.org/bugs/attachment.cgi?id=287188  expand "org.eclipse.swt.custom.StyledTextRenderer.getTextLayout" in Reverse calls

That "Compare with another heap dump..." feature is hard to find. i found it here: 

+1 @ghillairet would you mind to implement theming instead of custom color preferences? when the user selects dark theme  the editor looks unusable:  A general color/font theming editor...

very useful plugin, but unfortunately eclipse **freezes** when running ``` public static void main(String[] args) { for (int i=1;i

it's not a real world use case. i just wondered why `new RuntimeException("" + i).printStackTrace();` also does coloring but does not have that speed problem. feels like coloring the stacktrace...

https://github.com/eclipse-pde/eclipse.pde/issues/175#issuecomment-1311633626

converted to draft, since https://github.com/eclipse-platform/eclipse.platform/pull/864 was not merged yet

Changing workspace setting would not have helped on the issue, as the mixed line endings have been checked in without using eclipse see https://github.com/eclipse-jdt/eclipse.jdt.core/pull/1566#discussion_r1396690641 Using the oomphed workspace does already...

https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/issues/1573#issuecomment-1825814006 > You could setup a CI job which uses the output of `git ls-files --eol` to reject files which use unwanted line endings. that would be sufficient to me