[MCPE-21627] Interact packet to spammy

Client sends Interact Packet for each entity, player on map and even himself. Action field always equals 4 (InteractUpdate) and EntityRuntimeID field always 0. Server feels very bad.

Devices: Highscreen Pure F, Samsung Galaxy s3 mini

Comments 4

odigiman 2017-04-28T12:08:24Z

I can confirm this with multiple Android devices running 1.1.0.8 and 1.1.0.9. Sample output from a custom server:

{{
[12:07:13] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:13] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:13] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:13] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:13] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:13] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:13] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:13] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:13] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:13] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:13] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:13] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:13] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:13] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:14] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:14] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
[12:07:14] [Server thread/DEBUG]: Unhandled InteractPacket received from dktapps: 0x210400
}}

This spams constantly. Previously it would spam action 4 (mouseover?) when looking at an entity. Now it spams it constantly, all the time. If not looking at any entity, spams eid 0.

Niclas Olofsson 2017-05-03T08:37:40Z

Can confirm this on MiNET too, so doesn't seem to be a custom server thing trigger it.

odigiman 2017-05-11T12:10:28Z

```
2334 ms <- Write: InteractPacket - 210400
2382 ms <- Write: InteractPacket - 210400
2383 ms <- Write: InteractPacket - 210400
2434 ms <- Write: InteractPacket - 210400
2435 ms <- Write: InteractPacket - 210400
2482 ms <- Write: InteractPacket - 210400
2483 ms <- Write: InteractPacket - 210400
2527 ms <- Write: InteractPacket - 210400
2528 ms <- Write: InteractPacket - 210400
2573 ms <- Write: InteractPacket - 210400
2574 ms <- Write: InteractPacket - 210400
2638 ms <- Write: InteractPacket - 210400
2639 ms <- Write: InteractPacket - 210400
2688 ms <- Write: InteractPacket - 210400
2689 ms <- Write: InteractPacket - 210400
2738 ms <- Write: InteractPacket - 210400
2739 ms <- Write: InteractPacket - 210400
2788 ms <- Write: InteractPacket - 210400
2789 ms <- Write: InteractPacket - 210400
2837 ms <- Write: InteractPacket - 210400
2838 ms <- Write: InteractPacket - 210400
2871 ms <- Write: InteractPacket - 210400
2872 ms <- Write: InteractPacket - 210400
2921 ms <- Write: InteractPacket - 210400
2922 ms <- Write: InteractPacket - 210400
2971 ms <- Write: InteractPacket - 210400
2972 ms <- Write: InteractPacket - 210400
3038 ms <- Write: InteractPacket - 210400
3039 ms <- Write: InteractPacket - 210400
3088 ms <- Write: InteractPacket - 210400
3089 ms <- Write: InteractPacket - 210400
3124 ms <- Write: InteractPacket - 210400
3125 ms <- Write: InteractPacket - 210400
3177 ms <- Write: InteractPacket - 210400
```
This dump was obtained from a vanilla client connecting to a vanilla server by tracing client-sided execution.

Judging from the timings on this dump, it appears that this spam is actually being sent twice per tick. This is a very bad issue.

odigiman 2017-08-12T10:23:07Z

This issue is resolved as of 1.2.0.11 beta.