Bugzilla – Full Text Bug Listing
| Summary: | IBM JDK 8.0.5.0 ubuntu Core dump | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Diego Alcorta <dalcorta> | ||||||||||
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> | ||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||||||
| Severity: | major | ||||||||||||
| Priority: | P3 | CC: | stephan.herrmann | ||||||||||
| Version: | 4.8 | ||||||||||||
| Target Milestone: | --- | ||||||||||||
| Hardware: | PC | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | stalebug | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Diego Alcorta
Created attachment 271389 [details]
Snap files generated
Created attachment 271390 [details]
Javacore file generated
Created attachment 271391 [details]
Heapdump generated
If you need coredump file I will have to split it into two files since compressed is bigger than limit, uncompressed is 2 gigs Eclipse ini ha the -vm tag to launch eclipse with ibm java The fact that Eclipse needs memory should not surprise :) What makes you feel this is a bug? Any hints why in particular JDT/Core should be at fault? Does it happen with a fresh workspace, too? As you specifically mention IBM JDK, how does this behavior compare to when you use another JDK (Oracle or OpenJDK ...)? This happens with fresh install, and old install it happens with Neon, Oxygen and mars build THis doesn't happen with Openjdk Summarizing: any (tested) version of Eclipse + works fine with OpenJDK - throws OOME with IBM JDK right? At this point we could easily dismiss this, blaming IBM JDK, rather than Eclipse, but let's still try to understand better: Your command line (probably from eclipse.ini) contains some proprietary options: -XX:+UseG1GC -XX:+UseStringDeduplication. Do this have an impact on the problem? What if you remove and try again on both JDKs? Can you find the -Xmx threshold value, at which each JDK starts to throw OOME? (Reduce the value until you see OpenJDK throw OOME, then increase the value until you see IBM JDK working fine). BTW: I asked about fresh workspace, you answered "fresh install". Have you tried a fresh (empty) workspace as well? Created attachment 271392 [details]
eclipse.ini
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |