As a follow up, using that memory monitor, I figured out that my maxpermgen settings in my eclipse.ini file were not having any affect. Here is my comment on a eclipse bug about this:
--launcher.XXMaxPermSize does not correctly identify the JVM on Apple OSX. So the appropriate way to to set the MaxPermSize is to put -XX:MaxPermSize=??? after the -vmargs in eclipse.ini Also another confusing thing on OSX is that there are 2 eclipse.ini files: [Eclipse Install Folder]/eclipse.ini [Eclipse Install Folder]/Eclipse.app/Contents/MacOS/eclipse.ini to be safe you need to make this change in both. Here is bug if you are interested: https://bugs.eclipse.org/bugs/process_bug.cgi Scott Scott Cytacki wrote: > I found this nice memory monitor plugin for eclipse. I'm still figuring > out how well it works, but it looks good so far: > > You can download it from this eclipse bug. > https://bugs.eclipse.org/bugs/show_bug.cgi?id=92250 > It is the attachment called *Memory Monitor Plugin, version 1.0.1* > <https://bugs.eclipse.org/bugs/attachment.cgi?id=75329> > > I found this because I upgrated to eclipse 3.3.1 and have since gotten > lots of permgen out of memory errors. > > Scott > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
