Description Larry Johnson 2011-12-09 01:46:07 EST

Build Identifier: Another Inconsistent StackMap

I tried to develop a simple test case but could not. The situation that I have is reproducible but it references too many things to make it feasible to send as an example
The problem appears to be in the number of allowed global class variables permitted. In the problem class, there are about 60 global variables that include String, List, and many user defined classes. I build the code in Eclipse but execute the code outside of Eclipse. At the critical stage where the program is still working (no stackmap problem), if I add one more varialbe of type String, List, or a user defined class, the error occurs. I found that for the particular class, let us all it classX. It turns out that I have about 10 of these class instantiations. If instead of making instantiations of the form "classX clsA=null, clsB=null;" and so on, I make "classX[] clsX;" then the
problem goes away. I seem to be able to choose any value for the size of the array of classX. Thus my program now works and the only difference is that I use an array index value instead of a separate name for each classX instantiation.
It is not clear to me if this is an underlying problem of the other bug reports which have been filed. I made a simple test case with 88 separately named String variables, but I did not encounter the bug. If I find a simple test case I will send it. In the mean time, I thought this work around might be useful.

I set priority at "Normal" if the work around works. If the work around does not work for someone, the problem is devastating since development cannot continue.

Reproducible: Always

Steps to Reproduce:
1.Program that is on the edge -- near failure point
2.Add "String x;" and program will fail: Inconsistent stackmap ...
3.