NetBurner Community Forum

Normally Eclipse is remarkably stable, but today I ran into a fairly serious problem. The error message was "Internal Builder Exec Error: not enough quota is available to process this command." A project that had been building fine suddenly stopped building successfully, even after reverting to a prior successful build. I closed Eclipse, then reopened and got a message indicating (Can't remember message verbatim, but to the effect that) the previous Workspace config could not be reopened. A default (minimal) workspace config opened w/o most of my previous views, perspectives, and menu configurations loaded. Upon trying to get menus reestablished, items actually got worse and the menus in one case went totally blank before I decided to quit. When I tried to open Eclipse again, I once more got the "Internal Builder Exec Error....not enough quota" message, but this time Eclipse refused to even open until I restarted the PC. Upon reboot, I removed about half of the projects from my (previously sort of humongous) workspace. Eclipse opened fine although once again w/only a bare-essentials set of views, perspectives, and menus.

Has anyone seen anything like this before and figured out how to avoid it? Is it possible to have too big a workspace (~300 - 400 projects, ~3gb?)

Have you tried increasing memory allocated to eclipse?

NBEclipse.exe -vmargs -Xmx512m allocates 512MB. I ran into errors before I did this, although I can't remember if the one you saw was one of them.

Good question, but in this case, no. In the past, I've configured Eclipse to run with the add'l -vmargs when a specific project got to be very large. The projects I've been working on since the last install have not been too big: The little bargraph on the bottom right of the Eclipse window only shows memory usage of 23M of 41M total. I typically add the -vmargs launch when a project starts showing something like 50M of 60M available. So, no, I'm not running with the add'l -vmargs. In other words, in the past I've added the -vmargs to accomodate a large project, not a large workspace. Maybe it helps for both situations though? I confess to being a bit reticent to going back and experimenting... It didn't loook pretty! On the other hand, it would be nice to now how to avoid in the future!

Finally, it is worth noting, just to keep everyone on the same page, that the revision I'm using for this project is Rel22_rc2, not the most recent beta.

Thanks.