Bug? "code too large for try statement" in a Sub with no Try statement

[Alessandro71]

I have a cross platform (B4A/B4i) app which compiles fine on B4A, but the B4i compiler stops with the following message:

B4i line: 1179
End Sub
shell\src\com\powercruisecontrol\check\b4i_carmodel_subs_0.java:165: error: code too large for try statement
catch (Exception e) {
^
1 error

The referenced line is the "End Sub" of a Sub with no try/catch statements at all.
Looking at the java code, it looks like a try/catch is automatically inserted by the compiler.
Is there a workaround for this?

 

[Sandman]

Just curious, how many lines are in the try statement in the java code? And how many lines in B4i for that same section?

 

[Alessandro71]

B4i code: 550 lines
resulting java code: 162 lines

the code is actually a sub with a big CreateMap

note: while counting lines for answering your question, I noticed that the error occurs only in Debug mode.
Release mode is fine.

 

[stevel05]

Without seeing the code I'm guessing in the dark but can't you split the code. Use CreateMap for the elements that aren't going to fail and add the ones that might in a try block afterwards?

 

[Alessandro71]

...in a try block afterwards?

there is no try block at all

anyway, that's what I did: I split the sub into 2 different subs with less lines each.

 

[DonManfred]

there is no try block at all

there are try catch-blocks added if you compile the b4x-code to an app which results in java-files.

if you got this error one solution (probably the best) is to split up the sub into several smaller SUBs.

 

[Erel]

This error can happen with very large subs, in debug mode. It hits a limit of the Java compiler. As @DonManfred wrote, the solution is to split the large sub.

It sometimes happen when the developer puts the data inside the code. Something that isn't recommended.

 

[emexes]

the Java compiler

Java? on iOS?

 

[DonManfred]

Java? on iOS?

the TO is confusing things i guess.

only B4A and B4J generates java files.
On iOS is is another language.

Maybe forgot a compiler-directive

#if B4A

?

 

[Erel]

Yes. Java.

In debug mode, the process that runs on the PC is based on Java. It communicates with the device process.

 

[Alessandro71]

This error can happen with very large subs, in debug mode. It hits a limit of the Java compiler. As @DonManfred wrote, the solution is to split the large sub.

It sometimes happen when the developer puts the data inside the code. Something that isn't recommended.

this case is peculiar: the sub is not "large" (550 lines), but consisting of a CreateMap of objects.
i don't see how this kind of data can be put outside of the code.

dataset = CreateMap( _
    CAR1:    Array As Object(m_1, m_2), _
    CAR1:    Array As Object(m_1, m_3, m_4), _
...

anyway, as i said, i solved by splitting the sub

 

[emexes]

There is a 64k limit on modules, of either code or literal data or both (can't remember).

550 lines would average to 120 bytes per array of objects, and between the array descriptor and the objects and maybe associated garbage-keeping information, it wouldn't surprise me if an array of three objects was around that same size.

 

[Alessandro71]

"64k limit on modules" and it's 1981 all over again

 

[emexes]

"64k limit on modules" and it's 1981 all over again

The limit was discussed in a 2019 thread:

Select Case compiles ok but run no good

I know the Select Case statement is large. When i run the class it leads to this error. But when i compile, it is ok. Should I be concerned with this? Will it pose a problem if i don't split it? It did compile ok. B4A Version: 9.01.2 Java Version: 8 Parsing code. (0.45s) Building...

www.b4x.com

and it took me a while to find the more-detailed info on it because that page no longer exists:

https://www.javaworld.com/article/2073208/reproducing--code-too-large--problem-in-java.html

and there is another discussion of it at:

“Code too large” Compilation Error in Java | Baeldung

Learn what causes the compiler error "code too large", along with situations where we might encounter it and what we can do to fix it.

www.baeldung.com