Printable View
Yes, I found another condition too when I try change another peer name by another application...
Application 1:
On text message from peer on subchannel 0 (sent)-> Set name to Received$( "Lacewing" ) and Send text "I successful changed my name" to peer on subchanel 0.
Application 2:
Button is clicked and edit box <> "" -> Send text Edittext$( "Edit Box" ) and loop peer on channel.
You're sure that crashes the server and not the client?
Don't you think that the process wasn't successful until the name changed condition is triggered? For all you know you could be saying "I did it!" moments before the server tells you that name could not be set.Quote:
Originally Posted by QS
Yes, you can check it by yourself...
[Problem signature]:
[Problem Event Name]: APPCRASH
[Application Name]: LacewingServer.exe
[Version of application]: 0.0.0.0
[[Application Timestamp]: 4bdf1a4d
[The name of the module with an error]: Lacewing.dll
[Version of the module with the error:]: 0.0.0.0
[Timestamp module with an error]: 4bdf1a32
[Exception Code]: c0000005
[Transfer exception]: 0001d157
[OS Version]: 6.1.7600.2.0.0.256.1
[Locale ID]: 1045
[Additional Information 1]: 0a9e
[Additional Information 2]: 0a9e372d3b4ad19135b953a78882e789
[Additional Information 3]: 0a9e
[Additional Information 4]: 0a9e372d3b4ad19135b953a78882e789
i change it to:
Application 1:
On text message from peer on subchannel 0 (sent)-> Set name to Received$( "Lacewing" ).
On name set-> Send text "I successful changed my name" to peer on subchanel 0.
Application 2:
Button is clicked and edit box <> "" -> Send text Edittext$( "Edit Box" ) and loop peer on channel.
Still crash...
@Edit:
When I use lacewing.mfx (build 14) and LacewingServer.exe (build 14) then the crash occurs but when i use Lacewing mfx (build 14) and LacewingSerwer.exe (build 13) then it's works great...
It would be on name changed, wouldn't it?Quote:
Originally Posted by QS
Actually I don't think that matters if it's crashing.
Jamie, I confirmed the server crash. The client is fine, but the server does indeed crash with this simple thing:
Always: Conenct to "localhost" on port 6121
The client does not experiance a crash even after a few minuites, but the server crashes after a second or two. "LacewingServer.exe has encountered a problem and needs to close"
Wait, I ran the test again, and this time the server held up just fine! The client froze this time! Here is the server log until the client froze:
[22:51:18] Client ID 0 connected from 127.0.0.1
[22:51:18] Client ID 0 disconnected
[22:51:18] Client ID 0 connected from 127.0.0.1
[22:51:18] Client ID 1 connected from 127.0.0.1
[22:51:18] Client ID 1 disconnected
[22:51:18] Client ID 0 disconnected
As you can see, the same client conencted twice with different IDs. Apparently this can either cause the server to crash or the client to freeze. :\
Ahh wait, that crash. It's already fixed in build 15 (which isn't released yet, if you're wondering..)
Quote:
Originally Posted by Jamie
Yes and I can't change peer name when I use server build 14. so I must use server build 13.