[delfuego]

Hello; over the past week of using ME 7.1.1, I’ve experienced a bug with the MyEclipse Memory Monitor a few times that seems weird. Randomly, while developing, I’ll get an alert box pop up that says:

'MyEclipse Memory Monitor' has encountered a problem.

An internal error occurred during: "MyEclipse Memory Monitor".

Clicking the “Details” button yields:

"An internal error occurred during: "MyEclipse Memory Monitor".
committed = 33095680 should be < max 33030144

I’m assuming this is a bug… is there anything I can do to prevent it?

My myeclipse.ini file:

-startup
../../../../common/plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
--launcher.library
../../../../common/plugins/org.eclipse.equinox.launcher.carbon.macosx_1.0.101.R34x_v20080731
-clean
-configuration
../../../configuration
-vmargs
-Xms256m
-Xmx512m
-XX:PermSize=128m
-XX:MaxPermSize=256m
-Dorg.eclipse.swt.internal.carbon.smallFonts
-XstartOnFirstThread

My installation details:

*** Date: 
Thursday, April 23, 2009 11:39:56 AM EDT

** System properties:
OS=MacOSX
OS version=10.5.6
Java version=1.5.0_16


*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.1.1
Build id: 7.1.1-20090310


*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 7.1.1
Build id: 7.1.1-20090310




Eclipse Platform

Version: 3.4.1.r341_v20080731-9I96EiDElYevwz-p1bP5z-NlAaP7vtX6Utotqsu
Build id: M20080911-1700


Eclipse Java Development Tools

Version: 3.4.1.r341_v20080709-0800-7o7tEAfEF_U5qyUgrb2HAp539P97
Build id: M20080709-0800


Eclipse Graphical Editing Framework GEF

Version: 3.4.1.v20080806-67718083A56B4H2A3213573
Build id: 200809101400


Eclipse RCP

Version: 3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341
Build id: M20080703-0800


Eclipse Plug-in Development Environment

Version: 3.4.1.r341_v20080731-7T7U0E9mlRIuGUYviF_VP
Build id: M20080703-0800




Eclipse startup command=-os
macosx
-ws
carbon
-arch
x86
-showsplash
-launcher
/Volumes/JEL MyEclipse 7.1/myeclipse/myeclipse.app/Contents/MacOS/myeclipse
-name
Myeclipse
--launcher.library
/Volumes/JEL MyEclipse 7.1/myeclipse/myeclipse.app/Contents/MacOS//../../../../common/plugins/org.eclipse.equinox.launcher.carbon.macosx_1.0.101.R34x_v20080731/eclipse_1115.so
-startup
/Volumes/JEL MyEclipse 7.1/myeclipse/myeclipse.app/Contents/MacOS/../../../../common/plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
-clean
-configuration
../../../configuration
-keyring
/Users/jlevine/.eclipse_keyring
-consoleLog
-showlocation
-vm
/System/Library/Frameworks/JavaVM.framework

[Loyal Water]

delfuego,
Can you switch to a new workspace and try working there for a while. Does this problem persist in the new workspace as well?

How many projects do you have in your old workspace?

[delfuego]

I can’t really switch workspaces; I have 15 projects in my current workspace, and fifty-plus changes to the workspace prefs that I’d have to make to the new workspace in order to be functional and productive.

(And I have to say that honestly, the “switch workspace and try it” answer is one of the most irritating answers, because it asks your users to totally give up hours of their own time in order to work around problems with an application they own. I know that personally, I have enough invested in my workspace that switching to another one is a big, big effort, one I don’t have the luxury of engaging in on a regular basis.)

[Loyal Water]

We’ve filed a bug to investigate the issueMoving workspaces is a bit more straight forward that you might realize:
https://www.genuitec.com/forums/topic/troubleshoot-how-to-create-a-clean-workspace/ — incase you ever need to do it in the future.

Workspace corruption is one of the unfortunate side-effects that occurs when working with Eclipse-based apps for extended periods of times.

[Author]

Posts