RE: [aspectj-dev] Bugzilla Bug 44215 : Out of Memory null point er exc

["DiFrango, Ron" <ron.difrango@xxxxxxxxxxxxxx>]

Jeff,

None to my knowledge other than using ant to compile and ajbrowser.bat to
visualize it.  It is funny that this topic is also coming up AGAIN on the
users forum.

Thanks,

Ron

-----Original Message-----
From: Jeff Dalton [mailto:daltonj@xxxxxxxxx] 
Sent: Monday, January 12, 2004 12:28 PM
To: aspectj-dev@xxxxxxxxxxx
Subject: [aspectj-dev] Bugzilla Bug 44215 : Out of Memory null pointer
exceptions


Greetings,

I am wanted to follow up about this bug, since I haven't seen any posts
since 10/20 and I just wanted to check and see about any updates on it
since.  In particular, I was wondering if there were any workarounds or
temporary fixes that you might be able to suggest.

I have been trying to do do some weaving using AJDT 1.1.4, but have been
running into the wonderful null pointer exception caused by not enough RAM.
I have 512 MB of RAM and my project (Apache Cocoon) is ~5000 classes (48
MB), java has used over 450 MB (and still climbing..) before it throws the
null.  And because of the memory reclamation problem mentioned by Pete
Kalmus in the bug, I am forced to restart eclipse after every compile.

If there isn't a good workaround I guess the next step is for me to try and
weave it from the command line or with ant, which should buy me an extra
60-70 MB.

regards,

- Jeff

_______________________________________________
aspectj-dev mailing list
aspectj-dev@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/aspectj-dev
 
**************************************************************************
The information transmitted herewith is sensitive information intended only
for use by the individual or entity to which it is addressed. If the reader
of this message is not the intended recipient, you are hereby notified that
any review, retransmission, dissemination, distribution, copying or other
use of, or taking of any action in reliance upon this information is
strictly prohibited. If you have received this communication in error,
please contact the sender and delete the material from your computer.