pfSense

One of the reasons for the problem is that if many static routes are added to the settings, the pf2.6 system will crash.
For example, adding the ip list in the attachment to the system route will cause problems.

I can't replicate this at all, but your two files have numerous overlapping networks which is invalid. Input validation now rejects it but it may not have in the past.

129.226.0.0/16
140.143.0.0/16
140.179.0.0/16
140.205.0.0/16
140.206.0.0/15
140.210.0.0/16
140.224.0.0/16
140.237.0.0/16
140.240.0.0/16
140.242.223.0/24
140.242.224.0/24
140.243.0.0/16
140.246.0.0/16
140.249.0.0/16
140.250.0.0/16
140.255.0.0/16
140.75.0.0/16
203.55.2.0/23
203.55.4.0/24
210.32.0.0/12
210.51.0.0/16
210.52.0.0/15
210.82.0.0/15
211.136.0.0/13
216.228.126.0/24

Those networks are in both cn1.txt and cn2.txt, you can't have two routes to the same destination.

This is the result of ip aggregation. Duplicates should be removed.
Attachment file updated.