FATAL Crash

Post here your questions about SFS2X. Here we discuss all server-side matters. For client API questions see the dedicated forums.

Moderators: Lapo, Bax

Mrm83
Posts: 99
Joined: 17 Dec 2017, 04:02

FATAL Crash

Postby Mrm83 » 11 Mar 2020, 20:40

Updated to SFS 2.15 with the latest C# client, we are now experiencing fatal crash.. reason, unknown.

The error is:
03-11 16:41:30.469 8517 8569 E Unity : MethodAccessException: Attempt to access method 'Sfs2X.Bitswarm.IMessage.get_IsUDP' on type 'Sfs2X.Bitswarm.Message' failed.
03-11 16:41:30.469 8517 8569 E Unity : at Sfs2X.Core.SFSIOHandler.OnDataWrite (Sfs2X.Bitswarm.IMessage message) [0x00000] in <00000000000000000000000000000000>:0
03-11 16:41:30.469 8517 8569 E Unity : at Sfs2X.SmartFox.Send (Sfs2X.Requests.IRequest request) [0x00000] in <00000000000000000000000000000000>:0
03-11 16:41:30.469 8517 8569 E Unity : at ConnectionController.Update () [0x00000] in <00000000000000000000000000000000>:0
03-11 16:41:30.469 8517 8569 E Unity :
03-11 16:41:30.469 8517 8569 E Unity : (Filename: currently not available on il2cpp Line: -1)
03-11 16:41:30.469 8517 8569 E Unity :

Crash log:
03-11 16:41:30.541 9242 8777 F google-breakpad: Microdump skipped (uninteresting)
03-11 16:41:30.587 8517 8777 F libc : Invalid address 0xa89cfa00 passed to free: value not allocated
03-11 16:41:30.587 8517 8777 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 8777 (UnityMain)
03-11 16:41:30.636 9245 8569 F google-breakpad: Microdump skipped (uninteresting)
03-11 16:41:30.747 9246 9246 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-11 16:41:30.748 9246 9246 F DEBUG : Build fingerprint: 'samsung/dreamqltevl/dreamqltecan:7.0/NRD90M/G950WVLS2ARA1:user/release-keys'
03-11 16:41:30.748 9246 9246 F DEBUG : Revision: '12'
03-11 16:41:30.748 9246 9246 F DEBUG : ABI: 'arm'
03-11 16:41:30.748 9246 9246 F DEBUG : pid: 8517, tid: 8777, name: UnityMain >>> com.temp.temp <<<
03-11 16:41:30.748 9246 9246 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
03-11 16:41:30.768 9246 9246 F DEBUG : Abort message: 'Invalid address 0xa89cfa00 passed to free: value not allocated'
03-11 16:41:30.768 9246 9246 F DEBUG : r0 00000000 r1 00002249 r2 00000006 r3 00000008
03-11 16:41:30.768 9246 9246 F DEBUG : r4 a88b0978 r5 00000006 r6 a88b0920 r7 0000010c
03-11 16:41:30.768 9246 9246 F DEBUG : r8 ae47bdc8 r9 00000000 sl 00000400 fp a89cfa00
03-11 16:41:30.768 9246 9246 F DEBUG : ip 00000016 sp c5909328 lr f476cba7 pc f476f4a0 cpsr 200f0010
03-11 16:41:30.804 9246 9246 F DEBUG :
User avatar
Lapo
Site Admin
Posts: 21588
Joined: 21 Mar 2005, 09:50
Location: Italy

Re: FATAL Crash

Postby Lapo » 12 Mar 2020, 08:58

Hi,
this doesn't seem related to 2.15 very much.

The issue here is a crash during a UDP write on the client side.
Does this happen consistently every time?
Is there a way to reproduce?
Also what version is the Unity API?

Thanks
Lapo
--
gotoAndPlay()
...addicted to flash games
Mrm83
Posts: 99
Joined: 17 Dec 2017, 04:02

Re: FATAL Crash

Postby Mrm83 » 12 Mar 2020, 13:06

No , it doesn't happen consistently. never seen this crash before. happened 3 times yesterday after updating to the latest client as you suggested regarding my other issue with buddy nickname not persisting.

i've downgraded back to the previous version and i havn't crashed yet so far, so it could be with the latest client api maybe?

not sure how to reproduce. not really doing anything spectacular.. just moving character around and receiving npc movement packets.
Mrm83
Posts: 99
Joined: 17 Dec 2017, 04:02

Re: FATAL Crash

Postby Mrm83 » 12 Mar 2020, 16:06

Also seeing this on server side:

12 Mar 2020 | 12:08:24,109 | WARN | SocketWriter::UDP-2 | bitswarm.core.SocketWriter | | Problems in SocketWriter::UDP inner loop.
java.lang.NullPointerException
at com.smartfoxserver.bitswarm.core.SocketWriterV3.udpSend(SocketWriterV3.java:510)
at com.smartfoxserver.bitswarm.core.SocketWriterV3.access$12(SocketWriterV3.java:479)
at com.smartfoxserver.bitswarm.core.SocketWriterV3$UDPWriteRunner.run(SocketWriterV3.java:857)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

Ok, somehow the UDP setting messed up. Fixed it on server and this error is gone.
User avatar
coolboy714cp
Posts: 323
Joined: 06 Feb 2010, 02:45
Contact:

Re: FATAL Crash

Postby coolboy714cp » 12 Mar 2020, 18:42

Are you saying this happens when you turn the setting on? What server version are you using?
Mrm83
Posts: 99
Joined: 17 Dec 2017, 04:02

Re: FATAL Crash

Postby Mrm83 » 12 Mar 2020, 18:54

The original post happened after upgrading to 2.15 server, and latest unity api. I wasn't able to reproduce it after downgrading back.

The server UDP error I just posted was caused by Socket addresses setting in Server Config. Not sure how that suddenly broke. Patching up the Socket addresses setting fixed this particular error.
User avatar
coolboy714cp
Posts: 323
Joined: 06 Feb 2010, 02:45
Contact:

Re: FATAL Crash

Postby coolboy714cp » 12 Mar 2020, 19:18

Oh didn't see this post had already been resolved :lol: Glad you were able to fix the issue though!
User avatar
Lapo
Site Admin
Posts: 21588
Joined: 21 Mar 2005, 09:50
Location: Italy

Re: FATAL Crash

Postby Lapo » 13 Mar 2020, 15:01

Mrm83 wrote:No , it doesn't happen consistently. never seen this crash before. happened 3 times yesterday after updating to the latest client as you suggested regarding my other issue with buddy nickname not persisting.

i've downgraded back to the previous version and i havn't crashed yet so far, so it could be with the latest client api maybe?

It could be, but I bet if you try to reproduce it in the Unity Editor it will never happen.
The native error points at an exception in the compiled ARM code, which is something we have no control over as it's performed by the Unity compiler for Android.

Unless there's a specific trigger (i.e. calling a certain function or handling a certain event) that causes the crash 100% of the times, it's going to be difficult for us to provide a workaround or fix, because the problem occurs after the C# code is built for Android/ARM.

Let us know
Lapo

--

gotoAndPlay()

...addicted to flash games
Mrm83
Posts: 99
Joined: 17 Dec 2017, 04:02

Re: FATAL Crash

Postby Mrm83 » 13 Mar 2020, 18:08

Yeah. Wasn't able to reproduce in editor (at least i tried to mimic the exact same thing I did on device).

Could you please provide me more info regarding that error or info around that error so I can try and figure out what may be causing it on my end?

AFAIK, client is not sending anything by UDP and you mentioned that that error was caused by UDP write.
Leonidasos
Posts: 3
Joined: 29 Apr 2020, 12:45

Re: FATAL Crash

Postby Leonidasos » 29 Apr 2020, 17:00

Hi,
Looks like I've got the same problem
Server is in version 2.15 (patched 2.14) . Client UNITY API was updated to the newest version and target build is PC/Desktop

At first try socket addresses were binded to 0.0.0.0 next I changed it to fixed IP address

I've got tons of error in smartfox.log.

Code: Select all

29 Apr 2020 | 12:13:56,604 | WARN  | SocketWriter::UDP-3 | bitswarm.core.SocketWriter |     | Problems in SocketWriter::UDP inner loop.
java.lang.NullPointerException
        at com.smartfoxserver.bitswarm.core.SocketWriterV3.udpSend(SocketWriterV3.java:510)
        at com.smartfoxserver.bitswarm.core.SocketWriterV3.access$12(SocketWriterV3.java:479)
        at com.smartfoxserver.bitswarm.core.SocketWriterV3$UDPWriteRunner.run(SocketWriterV3.java:857)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
Attachments
server.zip
(1.37 KiB) Downloaded 22 times
User avatar
Lapo
Site Admin
Posts: 21588
Joined: 21 Mar 2005, 09:50
Location: Italy

Re: FATAL Crash

Postby Lapo » 30 Apr 2020, 07:29

At first try socket addresses were binded to 0.0.0.0 next I changed it to fixed IP address

Please revert it back to 0.0.0.0 (both tcp and udp)
There's no need to change the default value. It will auto-bind your network card(s) without the need for manual config.

Thanks
Lapo

--

gotoAndPlay()

...addicted to flash games
Leonidasos
Posts: 3
Joined: 29 Apr 2020, 12:45

Re: FATAL Crash

Postby Leonidasos » 30 Apr 2020, 12:38

Lapo wrote:
At first try socket addresses were binded to 0.0.0.0 next I changed it to fixed IP address

Please revert it back to 0.0.0.0 (both tcp and udp)
There's no need to change the default value. It will auto-bind your network card(s) without the need for manual config.

Thanks


UDP/TCP addresses set to 0.0.0.0 doesn't resolve this issue. As I mentioned it was my first configuration. I've changed addresses to fixed but it also didn't help.

Anyway I switched back to Smartfox 2.14 and there is no more spamming warnings about 'UDP loop'. I hope that you can reproduce it on 2.15..

Thanks
User avatar
Lapo
Site Admin
Posts: 21588
Joined: 21 Mar 2005, 09:50
Location: Italy

Re: FATAL Crash

Postby Lapo » 30 Apr 2020, 14:19

Hi,
I have no idea how to reproduce this. Can you give us a step by step description of how to reproduce?
Also specify which OS you're using and which client platform and API version you're using.

Thanks
Lapo

--

gotoAndPlay()

...addicted to flash games
Leonidasos
Posts: 3
Joined: 29 Apr 2020, 12:45

Re: FATAL Crash

Postby Leonidasos » 01 May 2020, 12:01

I've attached zip file with logs including application (extension) and Smartfox log.

There is not many steps to reproduce. Just 2 clients trying to login to game.
One interesting thing can be that there is a scheduled task running every 100ms and is responsible for populating data to clients, but this task works for us on 2.14 and all other earlier versions.

Server is running on: Linux 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Client is Windows Desktop
Client API: C# Version: 1.7.13
Attachments
logs.zip
(1.25 KiB) Downloaded 24 times
User avatar
Lapo
Site Admin
Posts: 21588
Joined: 21 Mar 2005, 09:50
Location: Italy

Re: FATAL Crash

Postby Lapo » 01 May 2020, 16:00

Sorry but the logs are not sufficient.
In order to reproduce the issue we need a step by step description of how to cause the problem.

We need to see what the client does and what the server does (if Extensions are involved)
If you prefer you can send the details privately via our support@... email box, with a reference to this discussion.

Thanks
Lapo

--

gotoAndPlay()

...addicted to flash games

Return to “SFS2X Questions”

Who is online

Users browsing this forum: No registered users and 25 guests