3023 was published on 1/12. 3024 didn’t publish until 1/20. So if you think you had the latest daily build for Stronghold, then it’s likely 3023.
Since you have a test case, you could drop back to 3023 and see if your test case has the error there.
Rob
I believe that you can use any JDK as long as its the 32 bit version.
Rob
I ask that because since a few time ago I have a lot of error.
The app kill by himself and there is a lot of glitch
Example of error:
\*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* Build fingerprint: 'Xiaomi/natrium/natrium:6.0.1/MXB48T/V8.2.2.0.MBGMIDL:user/release-keys' Revision: '0' ABI: 'arm' pid: 12495, tid: 12518, name: GLThread 360 \>\>\> com.Artha.goh \<\<\< signal 11 (SIGSEGV), code 2 (SEGV\_ACCERR), fault addr 0x3f8000ac r0 3f800000 r1 00000004 r2 f3ec4c40 r3 d7c48940 r4 da59d040 r5 ef5481ac r6 00000001 r7 d94ca390 r8 df383180 r9 00000000 sl 000002d0 fp 000000c0 ip f3f199c4 sp ef5481a0 lr f3c76fa8 pc f3c8b584 cpsr 200e0010 backtrace: #00 pc 000b8584 /data/app/com.Artha.goh-1/lib/arm/libcorona.so #01 pc 000a3fa4 /data/app/com.Artha.goh-1/lib/arm/libcorona.so #02 pc 000a45c4 /data/app/com.Artha.goh-1/lib/arm/libcorona.so #03 pc 0010ba7c /data/app/com.Artha.goh-1/lib/arm/libcorona.so #04 pc 0000cc04 /data/app/com.Artha.goh-1/lib/arm/liblua.so #05 pc 0000d004 /data/app/com.Artha.goh-1/lib/arm/liblua.so #06 pc 0001bf1c /data/app/com.Artha.goh-1/lib/arm/liblua.so #07 pc 0001cf60 /data/app/com.Artha.goh-1/lib/arm/liblua.so #08 pc 0000d050 /data/app/com.Artha.goh-1/lib/arm/liblua.so #09 pc 0000c35c /data/app/com.Artha.goh-1/lib/arm/liblua.so #10 pc 0000d1c8 /data/app/com.Artha.goh-1/lib/arm/liblua.so #11 pc 000055a0 /data/app/com.Artha.goh-1/lib/arm/liblua.so (lua\_pcall+88) #12 pc 000efc14 /data/app/com.Artha.goh-1/lib/arm/libcorona.so #13 pc 00084854 /data/app/com.Artha.goh-1/lib/arm/libcorona.so #14 pc 00129ac8 /data/app/com.Artha.goh-1/lib/arm/libcorona.so #15 pc 00076d90 /data/app/com.Artha.goh-1/lib/arm/libcorona.so #16 pc 0077b66d /data/app/com.Artha.goh-1/oat/arm/base.odex (offset 0x58c000)
Are there other useful messages that could help narrow this down?
Also what device is generating the error and what version of Android is it running?
Rob
Xiamomi Mi5 on android 6.01 Some other beta tester tell me that they have the same problems
The vertical line appear very often when we display a lot of new things (launch of a level)
I don’t see the issue on my Google Nexus 9 running Android 6.0.1. The JDK is used for code signing. It doesn’t alter your code in anyway. Basically the version of Java’s JDK shouldn’t have any impact on how your screen updates.
The error is a “segment violation” which means you’re trying to access some memory address your app doesn’t have access to. This can come from removing a scene that has a function that’s still being called by a timer or a Runtime enterFrame event.
Rob
Thank you for your reply
The problem can’t be from scene because in my game I don’t use them. Have you another idea on the reason of the bug and on the reason of the glitch (the vertical line)?
The bug is very often, on many device. 
I don’t know what I can do. For example on Jiayu S3 LTE Android 7.1.1 it’s bug very often like on Andy android emulator, like on Xiaomi Mi5…
On corona simulator I never have error
I realy need help
And sometime the app don’t want to open. Before the splash screen the app doesn’t respond
What version of Corona are you using?
Are there any messages in your device’s console log that may help us?
Rob
Hello,
I am using the build 2017.3068.
An exemple of error:
\*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* Build fingerprint: 'Xiaomi/natrium/natrium:6.0.1/MXB48T/V8.2.2.0.MBGMIDL:user/release-keys' Revision: '0' ABI: 'arm' pid: 29232, tid: 29262, name: GLThread 2012 \>\>\> com.Artha.goh \<\<\< signal 11 (SIGSEGV), code 1 (SEGV\_MAPERR), fault addr 0x6fd r0 00000651 r1 00000004 r2 f40a5e88 r3 d4abe100 r4 ea126f30 r5 ef6df1ac r6 00000001 r7 ef53fe90 r8 df54d300 r9 00000000 sl 000002d0 fp 000000c0 ip f40fa9c4 sp ef6df1a0 lr f3e57880 pc f3e6be5c cpsr 200f0010 backtrace: #00 pc 000b8e5c /data/app/com.Artha.goh-2/lib/arm/libcorona.so #01 pc 000a487c /data/app/com.Artha.goh-2/lib/arm/libcorona.so #02 pc 000a4e9c /data/app/com.Artha.goh-2/lib/arm/libcorona.so #03 pc 0010c3e8 /data/app/com.Artha.goh-2/lib/arm/libcorona.so #04 pc 0000cc04 /data/app/com.Artha.goh-2/lib/arm/liblua.so #05 pc 0000d004 /data/app/com.Artha.goh-2/lib/arm/liblua.so #06 pc 0001bf1c /data/app/com.Artha.goh-2/lib/arm/liblua.so #07 pc 0001cf60 /data/app/com.Artha.goh-2/lib/arm/liblua.so #08 pc 0000d050 /data/app/com.Artha.goh-2/lib/arm/liblua.so #09 pc 0000c35c /data/app/com.Artha.goh-2/lib/arm/liblua.so #10 pc 0000d1c8 /data/app/com.Artha.goh-2/lib/arm/liblua.so #11 pc 000055a0 /data/app/com.Artha.goh-2/lib/arm/liblua.so (lua\_pcall+88) #12 pc 000f052c /data/app/com.Artha.goh-2/lib/arm/libcorona.so #13 pc 00084e44 /data/app/com.Artha.goh-2/lib/arm/libcorona.so #14 pc 0012a49c /data/app/com.Artha.goh-2/lib/arm/libcorona.so #15 pc 00077004 /data/app/com.Artha.goh-2/lib/arm/libcorona.so #16 pc 007af685 /data/app/com.Artha.goh-2/oat/arm/base.odex (offset 0x5c1000)
Thanks
Are you getting the error your self or are you depending on error reports from users through Google Play? If you’re getting the error is there more to the error in your console log? Perhaps a backtrace above it in the log somewhere?
We really need more to go on. What you’ve posted above isn’t all that useful in finding the problem.
Rob
I am getting it by myself. This is the whole backtrace, I have copy past all the error who is display. Perhaps there is an other way, to get them but I haven’t find it. On the google play in error and ANR there is no error show.
Why this kind of error doesn’t generate “unhandledError” kind of error?
After analyse all these errors, I have discover it’s happen when we click multi time(very fast) on objects. A few time a go, the app don’t receive all this tap event.
To reproduce the error:
MyImage=display.newImage("test.png",1) function MyImage:tap(event) -- some stuff MyImage:removeSelf() MyImage=nil end MyImage:addEventListener("tap")
Before when we click a lot of time on the image the event happen only once and now it can happen a lot of time
If this is the cause of the crash, then I would suggest that either you write your function like:
function MyImage:tap(event) -- some stuff if MyImage and MyImage.removeSelf then MyImage:removeSelf() MyImage=nil end end
or
function MyImage:tap(event) -- some stuff display.remove(MyImage) MyImage=nil end
display.remove() basically checks to make sure the object exists before you try and remove it, including the check I used in the first block inside it’s code and is probably the preferred way to handle this issue.
Rob
I know I can do that to prevent that kind of problem. The stuff will be execute twice or more…But this isn’t the problem. before corona didn’t worked like this. I have 100 000 of lines of code on my project and I can’t correct all my code like this. The problem didn’t concern only me. It concern all corona’s users.
Like I said before I have found the solution to this problem and purpose a patch to it.
For the glitch bug: https://drive.google.com/drive/folders/0B5XGunixm_xqZ3ZWeEtfNEdMMDA?usp=sharing
(A few screenshots). The vertical line is from the previous image display.
It happen when we launch a level. When we move the map, the line disappear.
Do you know what Build you used for Stronghold? or a build that doesn’t have this crashing issue?
Thanks
Rob
I don’t remember with which version but the date of the last update is 18th of january (build with the last version of corona)
Do you need more information?