Ok, that's a good explanation for why you'd see this behavior: the weak
references aren't collected. I still don't understand why increasing the
stack size wouldn't fix the problem you saw also: it surely is a case of
just needing a few more stack frames.
_
From: [EMAIL PROTECTED]
[mai
That's what I'd expect too although I'm surprised at the error as reported:
the method with the stack overflow isn't in a new thread, so why would
increasing -Xmx avoid a stack overflow if stack is all allocated up front?
I do know that it's a weak map and for a good reason: this allows the
col
Oo... I bet that¹s it!! When memory gets low, the entries get cleared
to null causing infinite recursion when the code attempts to place a value
back into the map. It¹s probably a sequence of steps like this:
1. Low memory
2. Map entries cleared
3. Code executes to fill 1 or more
4. Low memo
Hi Kevin!
No, its a completely standard Sun 1.5.0_09 VM ;), and I do agree with
you about stack handling.
I had some trouble getting to the AspectJ source code (I don't
understand why don't we get a source distribution when the binaries are
released...), but I'm betting this problem is related to
