Bug 460880 - VMOOME in MirrorImpl.defaultReplyErrorHandler (284)
Summary: VMOOME in MirrorImpl.defaultReplyErrorHandler (284)
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 464356 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-02-26 01:15 EST by EPP Error Reports CLA
Modified: 2022-09-15 11:47 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description EPP Error Reports CLA 2015-02-26 01:15:51 EST
The following incident was reported via the automated error reporting:


    code:                   125
    plugin:                 org.eclipse.jdt.debug_3.8.200.v20140902-1837
    message:                Internal error logged from JDI Debug: 
    fingerprint:            4aa475be
    exception class:        com.sun.jdi.VMOutOfMemoryException
    exception message:      -
    number of children:     0
    
    com.sun.jdi.VMOutOfMemoryException: null
    at org.eclipse.jdi.internal.MirrorImpl.defaultReplyErrorHandler(MirrorImpl.java:284)
    at org.eclipse.jdi.internal.ObjectReferenceImpl.referenceType(ObjectReferenceImpl.java:517)
    at org.eclipse.jdt.internal.debug.core.model.JDIThread.determineIfDaemonThread(JDIThread.java:516)
    at org.eclipse.jdt.internal.debug.core.model.JDIThread.initialize(JDIThread.java:302)
    at org.eclipse.jdt.internal.debug.core.model.JDIThread.<init>(JDIThread.java:265)
    at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.newThread(JDIDebugTarget.java:566)
    at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.createThread(JDIDebugTarget.java:542)
    at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget$ThreadStartHandler.handleEvent(JDIDebugTarget.java:1967)
    at org.eclipse.jdt.internal.debug.core.EventDispatcher.dispatch(EventDispatcher.java:152)
    at org.eclipse.jdt.internal.debug.core.EventDispatcher.access$0(EventDispatcher.java:100)
    at org.eclipse.jdt.internal.debug.core.EventDispatcher$1.run(EventDispatcher.java:249)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
   
  

General Information:

    reported-by:      Marcel Bruch
    anonymous-id:     385b7d4a-7307-3cb4-8e18-f3645fdd9b3a
    eclipse-build-id: 4.5.0.I20140918-0330
    eclipse-product:  org.eclipse.epp.package.committers.product
    operating system: MacOSX 10.9.5 (x86_64) - cocoa
    jre-version:      1.8.0_20-b26

The following plug-ins were present on the execution stack (*):
    1. org.eclipse.core.jobs_3.6.100.v20140821-1523
    2. org.eclipse.jdt.debug_3.8.200.v20140902-1837
    3. org.eclipse.jdt_3.11.0.v20140918-0330

Please note that:
* Messages, stacktraces, and nested status objects may be shortened.
* Bug fields like status, resolution, and whiteboard are sent
  back to reporters.
* The list of present bundles and their respective versions was
  calculated by package naming heuristics. This may or may not reflect reality.

Other Resources:
* Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/54c4ef00bee810030da065c5  
* Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide


Thank you for your assistance.
Your friendly error-reports-inbox.
Comment 1 Sarika Sinha CLA 2015-04-10 02:52:18 EDT
*** Bug 464356 has been marked as a duplicate of this bug. ***
Comment 2 Eclipse Genie CLA 2020-08-21 13:06:06 EDT
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.

If you have further information on the current state of the bug, please add it. 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.
Comment 3 Eclipse Genie CLA 2022-09-15 11:47:44 EDT
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.

If you have further information on the current state of the bug, please add it. 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.