Peer2Peer issues

[Zach-Gasket]

Hello,

I have a couple issues cropping up with P2P, that I hope are springing from the same root cause. They are:

• Sometimes I receive a zero length packet
• Sometimes I get a warning about having a full queue, but with a ridiculously large number

Usually after them I'll get some form of disconnect or crash because I'm expecting packets. I am sending over a variety of packets, all on the same channel.

For the first issue, when it happens the result of GetNextReceivedPacketSize is SUCCESS and outPacketSizeBytes is retrieved as 0.

            uint uBytesAvailable;
            var getNextReceivedPacketSizeOptions = new GetNextReceivedPacketSizeOptions
            {
                LocalUserId = EOSManager.Instance.GetProductUserId(),
                RequestedChannel = 1
            };
           
            Result result = EOSManager.Instance.GetEOSP2PInterface().GetNextReceivedPacketSize(
                ref getNextReceivedPacketSizeOptions,
                out outPacketSizeBytes);

If I get the packetqueueinfo at this point it looks like
IncomingPacketQueueCurrentPacketCount: 0
IncomingPacketQueueCurrentSizeBytes: 40
IncomingPacketQueueMaxSizeBytes: 5242880
OutgoingPacketQueueCurrentPacketCount: 0
OutgoingPacketQueueCurrentSizeBytes: 0
OutgoingPacketQueueMaxSizeBytes: 5242880

Everything I send has at least two bytes in it however.

For the second issue, I am retrieving all packets available every ten ms and I get the following warning:

2023-01-11T16:19:13.1174657-08:00 LogEOSP2P(Warning): Unable to queue incoming packet, queue is full! QueueSize=[18446744073709551576/5242880] NewPacketSize=[80]
UnityEngine.Debug:Internal_Log(Int32, String, Object)
UnityEngine.Debug:LogWarning(Object)
PlayEveryWare.EpicOnlineServices.EOSManager:SimplePrintCallback(LogMessage&) (at D:\Perforce\test\game\source\thirdparty\EOSUnity\Runtime\EOSManager.cs:648)
Epic.OnlineServices.Logging.LoggingInterface:LogMessageFuncInternalImplementation(LogMessageInternal&) (at D:\Perforce\test\game\source\thirdparty\EOSUnity\Runtime\EOS_SDK\Generated\Logging\LoggingInterface.cs:52)
System.Object:wrapper_native_00007FFC56CB1B50(IntPtr, UInt64)
Epic.OnlineServices.Platform.PlatformInterface:Tick() (at D:\Perforce\test\game\source\thirdparty\EOSUnity\Runtime\EOS_SDK\Generated\Platform\PlatformInterface.cs:868)
PlayEveryWare.EpicOnlineServices.EOSManager:Tick() (at D:\Perforce\test\game\source\thirdparty\EOSUnity\Runtime\EOSManager.cs:1334)
a1.EpicAPIIntegration:Update() (at D:\Perforce\test\game\source\game\tmp\Wrapper\EpicAPIIntegration.cs:81)
a2:Update() (at D:\Perforce\test\game\source\game\tmp\main.cs:2286)

The last two digits of the number can vary. In binary that's 1111111111111111111111111111111111111111111111111111111111011000. It feels a lot like something has stomped some of the memory there.

Any help is appreciated, thank you!

[Zach-Gasket]

In case anyone is interested I'm still not sure why issues are showing up in this way, however it appears that this was caused because I was trying to access the packets in a different thread than the one that is EOSManager calls its tick on.

[paulhazen]

Hi @Zach-Gasket - almost a year after this discussion I can confirm that threading was the crux of the issue. It's since been resolved.