Why don't you have any information? The stack dump that comes with the
StackOverflowError should tell you where to start looking.

I think it's more likely that your stack *depth* has become too great,
for example in a recursive method (or set of mutually recursive
methods), not that one particular method has too many local variables.

/gordon

--

A stack frame overflow from too many function variables as opposed to a
poorly-written recursive call would require probably on the order of
hundreds, if not thousands, of local variables per function call.

Generally, when one gets a stack overflow, one gets the output like this:
...
   at Foo.bar(Foo.java:23)
   at Foo.bar(Foo.java:23)
   at Foo.bar(Foo.java:23)
   at Foo.bar(Foo.java:23)
   at Foo.bar(Foo.java:23)
   at Foo.bar(Foo.java:23)
   at Foo.bar(Foo.java:23)
   at Foo.bar(Foo.java:23)
...

indicating that the termination for recursion is not properly working.
The best thing to do would be to print diagnostics (e.g. the argument
list) and squirrel away the error to /dev/null.