Revision 2eb41b43bfbb6f6389462bc0304a05ef7e39fa04 authored by Igor Fedorenko on 12 May 2017, 22:37:01 UTC, committed by Andrey Loskutov on 05 July 2017, 15:20:08 UTC
Prevents JDI events fork large number of background jobs, which result in OutOfMemoryError: unable to create new native thread in extreme cases. Events are processed in the same order they were provided by the target jvm. Events that require expression evaluation are then forked to separate jobs (to avoid deadlock waiting on the main event processing job). Change-Id: Iddfff226dd101eb5288ae372b1511280e8fc7db8 Signed-off-by: Igor Fedorenko <igor@ifedorenko.com> Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
1 parent c102897
| File | Mode | Size |
|---|---|---|
| org.eclipse.jdt.debug | ||
| org.eclipse.jdt.debug.jdi.tests | ||
| org.eclipse.jdt.debug.tests | ||
| org.eclipse.jdt.debug.ui | ||
| org.eclipse.jdt.launching | ||
| org.eclipse.jdt.launching.macosx | ||
| org.eclipse.jdt.launching.ui.macosx | ||
| .gitignore | -rw-r--r-- | 101 bytes |
| CONTRIBUTING | -rw-r--r-- | 1.5 KB |
| pom.xml | -rw-r--r-- | 2.1 KB |
Computing file changes ...
