Null empty node

Issues GraphQL
1

Dgraph version : v23.0.0
Dgraph codename : dgraph
Dgraph SHA-256 : aafa0fe5a65059eec94703e2ed6d5c88a80317e9ee7e8c3776a6abf60ae78fc4
Commit SHA-1 : 38980bc
Commit timestamp : 2023-05-08 14:56:12 -0700
Branch : HEAD
Go version : go1.19.8
jemalloc enabled : true

In my self hosted DB sometimes I see a node that is null. Not that its fields are null but that actually the node itself has a type assigned but the data is null.
If I query for all the appliances of a it’s type I retrieve it, but it has no contents.

{
  "errors": [
    {
      "message": "Non-nullable field 'device' (type Device!) was not present in result from Dgraph.  GraphQL error propagation triggered.",
      "locations": [
        {
          "line": 31,
          "column": 3
        }
      ],
      "path": [
        "queryDevice",
        5,
        "device"
      ]
    },
    {
      "message": "Non-nullable field 'device' (type Device!) was not present in result from Dgraph.  GraphQL error propagation triggered.",
      "locations": [
        {
          "line": 31,
          "column": 3
        }
      ],
      "path": [
        "queryDevice",
        6,
        "device"
      ]
    }
  ],
  "data": {
    "queryDevice": [
      {
        "name": "marker",
        "myid": "00000000",
      },
...
      null,
      null,
      {
        "name": "name1",
        "myid": "11111111-1111-1111-1111-111111111111",
      },
...

My bet is that some memory is not deallocating properly and the pointer still exists but points to nowhere. I create and delete a lot of nodes using always the same mutations, and this only happens every so often.
Any bets on where the problem might be, or how could this be prevented or at least detected?