Old transactions stuck in cache for a very long time

[cedricfung]

If there are lots of transactions went into the cache pool, sometimes most of them will just stuck in the pool and never finalized, but new transactions seem work well.

[steal-7126]

If there are lots of transactions went into the cache pool, sometimes most of them will just stuck in the pool and never finalized, but new transactions seems to work perfectly well

[cedricfung]

The exact reason may be the bug in ordering the transactions cache queue, but I think the main cause is 0429e19878e6d4af86824799f62d05c994f4fc58

Because too many removed chains also contribute to the queue state because the network sync loop.

[cedricfung]

This is the possible cause, but recent situations showed that those QueueState were very small exactly, so it's very unlikely this.

		caches, finals, _ := node.QueueState()
		if caches > 1000 || finals > 500 {
			logger.Printf("LoopCacheQueue QueueState too big %d %d\n", caches, finals)
			continue
		}

[cedricfung]

This seems more like a wallet issue, not related to the kernel.