[Counter-Strike 2] Pango is causing journal flood

[Duckrinium]

Your system information

• System information from steam (Steam -> Help -> System Information) in a gist: https://gist.github.com/Duckrinium/cfa6b218bf6ac25b74a67a1fb2998e4e

• Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

Counter-Strike 2 is generating a lot (can reach to 50 entries per second) of journal entries related to Pango when in match.
example of few lines:

Dec 02 20:53:26 duckpc steam[2482]: (process:7051): Pango-CRITICAL **: 20:53:26.673: pango_layout_line_get_x_ranges: assertion 'start_index <= end_index' failed
Dec 02 20:53:26 duckpc steam[2482]: (process:7051): Pango-CRITICAL **: 20:53:26.687: pango_layout_line_get_x_ranges: assertion 'start_index <= end_index' failed
Dec 02 20:53:26 duckpc steam[2482]: (process:7051): Pango-CRITICAL **: 20:53:26.711: pango_layout_line_get_x_ranges: assertion 'start_index <= end_index' failed
Dec 02 20:53:26 duckpc steam[2482]: (process:7051): Pango-CRITICAL **: 20:53:26.724: pango_layout_line_get_x_ranges: assertion 'start_index <= end_index' failed

This seems to be related to other Pango related issues, though in my case game does not crash but journals grow pretty quickly in size and makes harder to read it.

Steps for reproducing this issue:

1. Open Counter-Strike 2
2. Join match (happens on Deathmatch, though haven't tested other modes)
3. Read journal, for example with journalctl or journalctl --follow for real-time view, observe journal is getting flooded.
4. Leaving match ceases the flood.