burst 1.4.0p4 e0.7 log spam "must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP"

Edit: as per #2, yes it's from upgrading to burst 1.3.0-preview.4 I believe
I've upgraded to Unity Entities 0.7.0 on the DOTSSample project and noticed I now get this error message on many methods when I build (with mono set )

Code (CSharp):

1. 2: The method `Int32 BeginSendMessage(Unity.Networking.Transport.NetworkInterfaceSendHandle ByRef, IntPtr)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
2. 2: The method `Int32 EndSendMessage(Unity.Networking.Transport.NetworkInterfaceSendHandle ByRef, Unity.Networking.Transport.NetworkInterfaceEndPoint ByRef, IntPtr, Unity.Networking.Transport.NetworkSendQueueHandle ByRef)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
3. 2: The method `Void AbortSendMessage(Unity.Networking.Transport.NetworkInterfaceSendHandle ByRef, IntPtr)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
4. 2: The method `Void Receive(Unity.Networking.Transport.NetworkPipelineContext ByRef, Unity.Networking.Transport.InboundRecvBuffer ByRef, Requests ByRef)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
5. 2: The method `Void Send(Unity.Networking.Transport.NetworkPipelineContext ByRef, Unity.Networking.Transport.InboundSendBuffer ByRef, Requests ByRef)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
6. 2: The method `Void InitializeConnection(Byte*, Int32, Byte*, Int32, Byte*, Int32, Byte*, Int32)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
7. 2: The method `Void Receive(Unity.Networking.Transport.NetworkPipelineContext ByRef, Unity.Networking.Transport.InboundRecvBuffer ByRef, Requests ByRef)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
8. 2: The method `Void Send(Unity.Networking.Transport.NetworkPipelineContext ByRef, Unity.Networking.Transport.InboundSendBuffer ByRef, Requests ByRef)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
9. 2: The method `Void InitializeConnection(Byte*, Int32, Byte*, Int32, Byte*, Int32, Byte*, Int32)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
10. 2: The method `Void Receive(Unity.Networking.Transport.NetworkPipelineContext ByRef, Unity.Networking.Transport.InboundRecvBuffer ByRef, Requests ByRef)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
11. 2: The method `Void Send(Unity.Networking.Transport.NetworkPipelineContext ByRef, Unity.Networking.Transport.InboundSendBuffer ByRef, Requests ByRef)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
12. 2: The method `Void InitializeConnection(Byte*, Int32, Byte*, Int32, Byte*, Int32, Byte*, Int32)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
13. 2: The method `Void Receive(Unity.Networking.Transport.NetworkPipelineContext ByRef, Unity.Networking.Transport.InboundRecvBuffer ByRef, Requests ByRef)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
14. 2: The method `Void Send(Unity.Networking.Transport.NetworkPipelineContext ByRef, Unity.Networking.Transport.InboundSendBuffer ByRef, Requests ByRef)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
15. 2: The method `Void InitializeConnection(Byte*, Int32, Byte*, Int32, Byte*, Int32, Byte*, Int32)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
16. 2: The method `Void Receive(Unity.Networking.Transport.NetworkPipelineContext ByRef, Unity.Networking.Transport.InboundRecvBuffer ByRef, Requests ByRef)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
17. 2: The method `Void Send(Unity.Networking.Transport.NetworkPipelineContext ByRef, Unity.Networking.Transport.InboundSendBuffer ByRef, Requests ByRef)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
18. 2: The method `Void InitializeConnection(Byte*, Int32, Byte*, Int32, Byte*, Int32, Byte*, Int32)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!
19. 2: The method `Void InvokeExecute(Parameters ByRef)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!

Code (CSharp):

1. 63: The method `Void RunWithoutJobSystem(Unity.Entities.ArchetypeChunkIterator*, Void*)` must have `MonoPInvokeCallback` attribute to be compatible with IL2CPP!

and this one many times

 

I updated to Burst to 1.3.0 preview 4 and tried it out while still having Entities at 0.6.0 and I also get this just by entering playmode. Also I consistently crash the editor when stepping a frame in playmode. Happens when I set the Project settings to il2cpp or mono.

 

I have a few other issues.

Terrible performance on NativeArray.CopyTo - takes 35ms on a 1million length array in a burst job. Turning off burst makes it take a fraction of the time.

Collections + entities + 0.7 seem to throw not unmanaged type when adding to a native stream, even if the struct is unmanaged...

needless to say, we have deferred our upgrade.

 

From Burst 1.3.0-preview.4 changelog:

 

I see that though was puzzled that it would print regardless if IL2CPP is chosen

 

1.3 regression over 1.2.3

Haven't tested p3, p2 was broken for us so we were waiting.

Was simply a native array copy to native array of type byte. Nothing else in job (allocation or anything).

Will post exact code when I get to work in like 6 hours.

 

Crash only happens in p4 for me, and only happens with safety checks disabled. (Safety checks disabled in p3 work normally). Case is 1124920

 

Editor (with all safety checks off, job debugger etc). We didn't get around to pushing it to build server before I reverted upgrade so I did not check.

Be at work in 90min, but from memory the job just looked something like this

Code (CSharp):

1. [BurstCompile]
2. public struct CopyJob : IJob {
3.  
4.    // Length 1024x1024
5.    public NativeArray<float> Array1;
6.    public NativeArray<float> Array2;
7.  
8.    public void Execute()
9.    {
10.        Array1.CopyTo(Array2);
11.    }
12. }

Very simple, should just be a memcpy but was taking 35ms on a 3700x.
Turning off burst on the job made it take less than 2ms.

 

Is there any documentation for this attribute? How can I solve it?

 

1124920 Crash after long lag with Burst
I submitted this bug on the first crash before I knew the culprit and before I knew I was going to reproduce it consistently. The long lag was due to a bug in CollisionConversionSystem.cs, but the crashes still happen even with that bug fixed. That system isn't required to run and reproduce the crash.

Even after a major refactor I made last night where I switched a bunch of stuff from using UnsafeUtility to using StructLayout Explicit, I'm still reproducing the issue this morning. If you can't reproduce it with the benchmark project I sent you last week, I can try and send you the latest version. Its the same scene, same project, same workflow. Crashes on the second frame before I ever see profiler data.

 

All i found was this: https://docs.microsoft.com/en-us/do...vokecallbackattribute?view=xamarin-ios-sdk-12 but i am also curious on how to correctly set this attribute.

Using the GoInGameRequest example, It throws this warning for both InvokeExecute and CompileExecute

Code (CSharp):

1.     // RPC request from client to server for game to go "in game" and send snapshot / inputs
2.     [BurstCompile]
3.     public struct GoInGameRequest : IRpcCommand {
4.         // Test int value
5.         public int value;
6.  
7.         public void Serialize(ref DataStreamWriter writer) {
8.             writer.WriteInt(value);
9.         }
10.  
11.         public void Deserialize(ref DataStreamReader reader) {
12.             value = reader.ReadInt();
13.         }
14.  
15.         [BurstCompile]
16.         private static void InvokeExecute(ref RpcExecutor.Parameters parameters) {
17.             RpcExecutor.ExecuteCreateRequestComponent<GoInGameRequest>(ref parameters);
18.         }
19.  
20.         public PortableFunctionPointer<RpcExecutor.ExecuteDelegate> CompileExecute() {
21.             return new PortableFunctionPointer<RpcExecutor.ExecuteDelegate>(InvokeExecute);
22.         }
23.     }

I dont like guessing, but something like this?

Code (CSharp):

1.         [BurstCompile, MonoPInvokeCallback(typeof(PortableFunctionPointer<RpcExecutor.ExecuteDelegate>))]
2.         private static void InvokeExecute(ref RpcExecutor.Parameters parameters) {
3.             RpcExecutor.ExecuteCreateRequestComponent<GoInGameRequest>(ref parameters);
4.         }

But i have no idea for CompileExecute.

 

Am getting this too with the Netcode samples. When _running_ my server.

Burst 1.3.0 preview 11
Entities 0.9.1 preview 15