Too much information in the blocks field of the graphql query results in an oom exception

[pengzhepz]

System information

Alaya version: alaya version 0.16.3
OS & Version: Windows/Linux/OSX
Commit hash : (if develop) 7fb9d1a

Actual behaviour

Use the following query：
{blocks(from: 1) {transactionCount ommerCount number hash nonce
parent {hash}
transactionsRoot
stateRoot
receiptsRoot
miner {address code balance transactionCount}
extraData
gasLimit
gasUsed
timestamp
logsBloom
mixHash
difficulty
totalDifficulty
ommerCount
ommers {transactionCount ommerCount}
ommerAt(index: 0) {transactionCount ommerCount}
ommerHash
transactions {index status gasUsed cumulativeGasUsed}
transactionAt (index:0){index status gasUsed cumulativeGasUsed}
logs (filter:{}) {index}
}
If there are many chained blocks, it will lead to memory overflow

[cheng762]

If the number of query blocks is too large, it will take up a lot of memory. This is not a memory leak, but insufficient memory.