Forum Discussion
I play on ios and android and emulators. They all have the same symptoms. This isn't a post hoc fallacy, there are issues, and we don't know what causes them, but they are replicated over different devices.
I don't care if it's "hard" to work out. If you run a business that releases something that doesn't work for your clients, you fix it. End of. If ran my businesses with the same laissez faire attitude that CG did I would have folded many years ago.
I realise you have to be impartial because of your positions, but frankly you're blinded by loyalty.
07-21 10:25:49.230 30303 31675 E CRASH : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
07-21 10:25:49.230 30303 31675 E CRASH : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-21 10:25:49.230 30303 31675 E CRASH : Build type 'Release', Scripting Backend 'il2cpp', CPU 'armeabi-v7a'
07-21 10:25:49.230 30303 31675 E CRASH : Build fingerprint: 'samsung/gts210wifixx/gts210wifi:7.0/NRD90M/T810XXU2DRH1:user/release-keys'
07-21 10:25:49.230 30303 31675 E CRASH : Revision: '6'
07-21 10:25:49.231 30303 31675 E CRASH : pid: 30303, tid: 31675, name: UnityMain >>> com.ea.game.starwarscapital_row <<<
07-21 10:25:49.231 30303 31675 E CRASH : r0 00000000 r1 036e8038 r2 00000000 r3 000f7e3d
07-21 10:25:49.231 30303 31675 E CRASH : r4 643488e8 r5 00004000 r6 00004000 r7 00040000
07-21 10:25:49.231 30303 31675 E CRASH : r8 00000000 r9 00000000 sl 814537cc fp 855feca0
07-21 10:25:49.231 30303 31675 E CRASH : ip 855fec90 sp 855fec98 lr 814818c8 pc 7dd3c0fc cpsr 617fdd90
07-21 10:25:49.231 30303 31675 E CRASH :
07-21 10:25:49.231 30303 31675 E CRASH : backtrace:
07-21 10:25:49.490 30303 31675 E CRASH : #00 pc 008d40fc /data/app/com.ea.game.starwarscapital_row-2/lib/arm/libil2cpp.so
07-21 10:25:49.490 30303 31675 E CRASH : #01 pc 008db388 /data/app/com.ea.game.starwarscapital_row-2/lib/arm/libil2cpp.so
07-21 10:25:49.490 30303 31675 E CRASH : #02 pc 031debdc /data/app/com.ea.game.starwarscapital_row-2/lib/arm/libil2cpp.so
07-21 10:25:49.490 30303 31675 E CRASH : #03 pc 031df1c8 /data/app/com.ea.game.starwarscapital_row-2/lib/arm/libil2cpp.so
07-21 10:25:49.490 30303 31675 E CRASH : #04 pc 01724cf8 /data/app/com.ea.game.starwarscapital_row-2/lib/arm/libil2cpp.so
07-21 10:25:49.490 30303 31675 E CRASH : #05 pc 01e45bb0 /data/app/com.ea.game.starwarscapital_row-2/lib/arm/libil2cpp.so
07-21 10:25:49.490 30303 31675 E CRASH : #06 pc 01f24f78 /data/app/com.ea.game.starwarscapital_row-2/lib/arm/libil2cpp.so
07-21 10:25:49.490 30303 31675 E CRASH :
- wharp956 years agoSeasoned Veteran@Resmi9793 What I was meaning is, how EA/CG can retrieve clients logs ? There is now way unless, the application have root access or they have a handler catching those signals then writing the crash stack into their own files and I don't see any reports uploading when I play (hidden?).
- 6 years ago
I've also done a little more digging today... The crash followed the usual symptoms of some graphical glitches followed by a total freeze.
Looking through the rest of the log, I saw some systemic memory failures, which was interesting because the only application I had running was SWGOH. Looking at the stack trace, it is another example of a null pointer issue. This is often a failure mode in C/C++ applications when they fail to aloocate memory (and then don't check if the allocation failed). So my working hypothesis is that we still have memory issues.
Fortunately, this time I was running the adb shell at the same time, so can compare the memory usage of SWGOH at the time of the crash and after normal operation.
Crash:
PID USER PR NI CPU% S #THR VSS RSS PCY Name
30303 u0_a211 16 -4 3% S 102 3080860K 850216K fg com.ea.game.starwarscapital_row
Normal operation:
PID USER PR NI CPU% S #THR VSS RSS PCY Name
31616 u0_a211 16 -4 9% S 102 2137360K 638212K fg com.ea.game.starwarscapital_row
The key thing to note here is that the crash is trying to use nearly 1GB more memory (VSS) than in normal operation. I suspect that there is something causing the application to leak memory over time.
My guess is that the devices seeing more crashes are ones that have smaller RAM, or for some reason are hitting the condition that causes the memory leak more often.
Would anyone in Support like to review and comment on my analysis?
- wharp956 years agoSeasoned Veteran
@Resmi9793it seems, the issue is now flagged for further investigation on this post:
https://answers.ea.com/t5/Bug-Reports/Crash-in-arena-match-SLKR-vs-SLKR/m-p/9332083#M40960
Finally ! - MomawNadonE3P06 years agoRising AdventurerBased on my own previous bug experience*, I'm not too optimistic that we'll get a timely or transparent response to this.
* frequent error code 106 crashes, for almost a year and a half now - my bug report was never even acknowledged, just merged into another thread where the only feedback given was a useless and ineffective cookie cutter response to try reinstalling ... and now I have a second type of crashing to deal with on a daily basis. Great.
About SWGOH Technical Issues
Recent Discussions
- 14 minutes ago
- 3 hours ago
- 4 hours ago