Why this command can cause a "trie is already committed"

[ethever]

System information

Geth version: geth version
CL client & version: e.g. lighthouse/nimbus/[email protected]
OS & Version: Windows/Linux/OSX
Commit hash : (if develop)

root@ser7:~# geth version 
Geth
Version: 1.13.14-stable
Architecture: amd64
Go Version: go1.22.0
Operating System: linux
GOPATH=
GOROOT=

root@ser7:~# evm --version 
evm version 1.13.14-stable

Expected behaviour

The trie should not be commited

Actual behaviour

"trie is already committed"

Steps to reproduce the behaviour

evm  --prestate /tmp/a.json --gas 10000 --sender 0x0dfa72de72f96cf5b127b070e90d68ec9710797c --receiver 0x0ad62f08b3b9f0ecc7251befbeff80c9bb488fe9 --value 0x00 --input e9ca826c000000 --json --dump run

Backtrace

root@ser7:~# evm  --prestate /tmp/a.json --gas 10000 --sender 0x0dfa72de72f96cf5b127b070e90d68ec9710797c --receiver 0x0ad62f08b3b9f0ecc7251befbeff80c9bb488fe9 --value 0x00 --input e9ca826c000000 --json --dump run
{"output":"","gasUsed":"0x0"}
INFO [03-31|14:32:56.029] Trie dumping started                     root=56e81f..63b421
ERROR[03-31|14:32:56.029] Trie dumping error                       err="trie is already committed"
{
    "root": "56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
    "accounts": {}
}

here is my a.json:

root@ser7:~# cat /tmp/a.json 
{"difficulty":"0x01","coinbase":"0x0000000000000000000000000000000000000000","timestamp":"0x00","number":"0x00","gasLimit":"0x3d0900","extraData":"0x00","mixhash":"0x0000000000000000000000000000000000000000000000000000000000000000","parentHash":"0x0000000000000000000000000000000000000000000000000000000000000000","nonce":"0x00","alloc":{},"config":{"eip150Block":0,"eip155Block":0,"eip158Block":0,"homesteadBlock":0,"daoForkBlock":0,"byzantiumBlock":2000,"constantinopleBlock":2000}}