Compiler crash

[Marcob]

Hello,

When I compile a program, sometimes the compiler crashes and the only way to restart B4A is to re-boot the PC (even killing the processes wont help).
The odd thing is that the first time after a PC boot it always works and generates the .apk file as expected, then after a successive compilation it fails.
I noted that before the compiler crashes the last line of message window reports: "Copy libraries resources".

Until now I never had this problem, now the only thing different from the past is that the program uses a custom library.

Is there anyone here that has experienced a similar issue ?

PS
This happen both with v2.52 and v2.71 version

 

[Erel]

Is there any error message when that happens?

 

[Marcob]

Is there any error message when that happens?

No. The progress bar of the compiler window freezes and the last line reports "Copy libraries resources", then the program B4A become "Not responding" and there is no way to close it. Also killing the process with task manager doesn't work (I'm running B4A under WinXP/AMD Phenom 9550/4GB ram). After the crash the only way to close B4A is to turn off the PC...

I noted that the crash problems arises only with my last program that uses a custom library (an USB driver created from a Java source). I made some different tests just using the option compile (without signing) and:

- If I run the compiler with no other programs running, it works
- If I run the compiler with Eclipse and other programs like Firefox running, it works
- If I run the compiler with the virtual device started, it crashes. Then if I run another instance of B4A trying to compile a different program it works but if I try to compile the program that caused the crash on the first b4A instance, the compiler warns that the file temp.ap_ cannot be accessed because it is in use by another process (and in this case the compiler doesn't crash).

 

[Erel]

Can you send me the suspected library ([email protected])?

 

[Marcob]

Can you send me the suspected library ([email protected])?

I've just sent you a pm. Thank you.

 

[Erel]

I'm unable to reproduce it. There are two small files in the library jar that are not needed (.classpath and .project) and are copied during this step. Try to remove them.

 

[Marcob]

I'm unable to reproduce it.

Did you have a virtual device running during your test ? Without a valid Android device (virtual or real), the "compile (without signing)" command still works smoothly.

There are two small files in the library jar that are not needed (.classpath and .project) and are copied during this step. Try to remove them.

This was a really good advice, thank you! Without that files the compiler doesn't crash anymore :sign0098: