Fatal signal 11 with beta 2.50

[Informatix]

Hello,

I have reports from my customers about your new version 2.50 (beta). When they use my UltimateListView product with it, they get a Fatal signal 11 (SIGSEGV), i.e. a violent crash. Some examples work, some others don't. Since my product doesn't use any special memory trick or system hack, and works fine with B4A v2.30, it seems there's a bug in your new version. Unfortunately, I don't have the new version (and for obvious reasons with beta versions, I prefer to not install it), so I cannot help a lot. I can provide you with logs sent by users. Here's one of them (unfiltered).
If you have no clue about this, I will install a virtual box on my computer to test the new version.

 

[Erel]

There is nothing in the logs that can tell what is the problem. You can download v2.50 and install it side by side with other versions.

This version doesn't change any native staff or memory management.

 

[Informatix]

There is nothing in the logs that can tell what is the problem. You can download v2.50 and install it side by side with other versions.

This version doesn't change any native staff or memory management.

Could you send me a link for this version ?

 

[Erel]

I've sent you a mail.

 

[Informatix]

I've sent you a mail.

By looking at your changes, it seems to me you reintroduced the bug with BringToFront in the ViewWrapper (but that's not the reason for the crashes).

 

[Erel]

There was no bug in BringToFront.

I decided to return to the previous implementation after this issue: http://www.b4x.com/forum/bugs-wishlist/23846-bringtofront-image-not-working.html#post138023

The native BringToFront is quite problematic. If you need it you can call it with reflection.

 

[Informatix]

There was no bug in BringToFront.

I decided to return to the previous implementation after this issue: http://www.b4x.com/forum/bugs-wishlist/23846-bringtofront-image-not-working.html#post138023

The native BringToFront is quite problematic. If you need it you can call it with reflection.

It's what I call a bug: when something does not work as expected and we have to use a workaround. For http://www.b4x.com/forum/bugs-wishlist/23846-bringtofront-image-not-working.html#post138023, why don't you suggest instead to call the invalidate method of the container (panel or activity holding the view) to refresh the children display ? I'm pretty sure that will solve the problem.

 

[Informatix]

OK, I found the reason for the crash: B4Aclass is now an interface. I solved the problem easily: I just recompiled my Java code with the new B4A JARs.

 

[Erel]

Invalidate will not help in that case (if I remember correctly).

View.BringToFront works correctly. It brings the view to the front. The case we discussed in the past was an "edge" case.

 

[thedesolatesoul]

OK, I found the reason for the crash: B4Aclass is now an interface. I solved the problem easily: I just recompiled my Java code with the new B4A JARs.

But is this new JAR backwards compatible?

 

[Informatix]

Invalidate will not help in that case (if I remember correctly).

It's not the view method that must be called, but its parent method (in an activity, call the activity.invalidate, in a panel, call the panel.invalidate). It's a case I encountered for other reasons and that's related to JellyBean. I just tried it and that solved the issue (in an activity and in a panel).

 

[Informatix]

But is this new JAR backwards compatible?

No. If you use B4A v2.3 you have to use the library version 1.2. If you use B4A v2.5, you have to use the library version 1.25.
I'm going to send a link to the new library to everyone.

 

[Erel]

I'm pretty sure that will solve the problem.

Seems like you are correct. However as the current method works properly it will not be changed.

 

[thedesolatesoul]

No. If you use B4A v2.3 you have to use the library version 1.2. If you use B4A v2.5, you have to use the library version 1.25.
I'm going to send a link to the new library to everyone.

Does this mean all libraries have to be re-compiled for B4A 2.50?
Or those that reference the B4A Class in a specific way?

 

[Informatix]

Does this mean all libraries have to be re-compiled for B4A 2.50?
Or those that reference the B4A Class in a specific way?

Only CallSubExtended is concerned.

 

[thedesolatesoul]

Only CallSubExtended is concerned.

Okay, thanks.