Searching the pedia for the first time after freshly launching the game (meaning the no games got started or joined yet).
this bug appears to behave differently depending on how the game was built where some builds have occur regardless of the value "effect proccesing threads (user interface)" and always with the same error while others only occur when "effect precessing threads (user interface)" > 1 crashes the game and with different errors (as expected from a multithreaded issue), I will be referring to the later as type-a and the former as type-b
Type-A
Details: MAY only occur when "effect precessing threads (user interface) is larger than 1 and occurs with different error messages
Affected Versions:
v0.5.1-rc1 (built for pacman systemwide install)
ced64f from the font_safety branch + 1 unrelated personal patch for continuous turning (built for pacman systemwide install)
Steps to reproduce:
- Make sure that "effect proccesing threads (user interface)" is more than one (setting it to a large number such 16 threads causes the issue to (almost?) always occur while 2 has ~50% chance)
- Exit the game (just to be sure)
- Launch the game
- Select pedia from main menu
- Click the search bar and input a text (for example "laenfa")
- Press Enter
- Enjoy the crash (or exit and do it again if it didn't occur this time and don't forget that you can increase "effect proccesing threads (user interface)" setting to increase the chance of crashing)
Reproduction Notes:
- If the crash doesn't occur the first time it won't occur
- Selecting an entry from the pedia works but has no effect on the occurence of this crash
- If you join a game and quit to menu the crash can no longer occur
- Setting "effect proccesing threads (user interface)" to 1 prevents this crash
Output: has shown multiple errors including (Note: first error only occured with the patched version which was tested more extensively)Building note: building for a systemwide pacman install uses the followingType-b
Always occurs regardless of the value of "effect precessing threads (user interface) and always gives the same output (at least for a given version)
Affected version:
- v0.5.1-rc1 (built normally via
- 33ddd3c (may have been built normally but idr, only here for completness)
- Arch linux freeorion-0.5.0.1-2 (system-wide install mostly built as mentioned above with minor patches)
Steps to reproduce:
- Launch the game
- Select pedia from main menu
- Click the search bar and input a text (for example "laenfa")
- Press Enter
- Enjoy the crash
Output:
for v0.5.1-rc1 and 33ddd3c:for arch linux freeorion-0.5.0.1-2:
this bug appears to behave differently depending on how the game was built where some builds have occur regardless of the value "effect proccesing threads (user interface)" and always with the same error while others only occur when "effect precessing threads (user interface)" > 1 crashes the game and with different errors (as expected from a multithreaded issue), I will be referring to the later as type-a and the former as type-b
Type-A
Details: MAY only occur when "effect precessing threads (user interface) is larger than 1 and occurs with different error messages
Affected Versions:
v0.5.1-rc1 (built for pacman systemwide install)
ced64f from the font_safety branch + 1 unrelated personal patch for continuous turning (built for pacman systemwide install)
Steps to reproduce:
- Make sure that "effect proccesing threads (user interface)" is more than one (setting it to a large number such 16 threads causes the issue to (almost?) always occur while 2 has ~50% chance)
- Exit the game (just to be sure)
- Launch the game
- Select pedia from main menu
- Click the search bar and input a text (for example "laenfa")
- Press Enter
- Enjoy the crash (or exit and do it again if it didn't occur this time and don't forget that you can increase "effect proccesing threads (user interface)" setting to increase the chance of crashing)
Reproduction Notes:
- If the crash doesn't occur the first time it won't occur
- Selecting an entry from the pedia works but has no effect on the occurence of this crash
- If you join a game and quit to menu the crash can no longer occur
- Setting "effect proccesing threads (user interface)" to 1 prevents this crash
Output: has shown multiple errors including (Note: first error only occured with the patched version which was tested more extensively)
Code:
terminate called after throwing an instance of 'GG::Font::BadGlyph' what(): GG::Font::Init : Face too large for buffer. First glyph to no longer fit: '3'AbortedCode:
terminate called after throwing an instance of 'std::runtime_error' what(): OptionsDB::Add<>() : Option registered twice: ui.design.selector.initializedAbortedCode:
malloc(): unaligned tcache chunk detectedAbortedCode:
double free or corruption (fasttop)Segmentation faultCode:
Segmentation faultCode:
pkgname=freeorionbuild() { cmake \ -B build \ -S "$pkgname" \ -DCMAKE_INSTALL_PREFIX=/usr \ -DCMAKE_BUILD_TYPE=Release gamemoderun cmake --build build -j8}package() { DESTDIR="$pkgdir" cmake --install build}Always occurs regardless of the value of "effect precessing threads (user interface) and always gives the same output (at least for a given version)
Affected version:
- v0.5.1-rc1 (built normally via
- 33ddd3c (may have been built normally but idr, only here for completness)
- Arch linux freeorion-0.5.0.1-2 (system-wide install mostly built as mentioned above with minor patches)
Steps to reproduce:
- Launch the game
- Select pedia from main menu
- Click the search bar and input a text (for example "laenfa")
- Press Enter
- Enjoy the crash
Output:
for v0.5.1-rc1 and 33ddd3c:
Code:
terminate called after throwing an instance of 'GG::SubTexture::BadTexture' what(): Attempted to construct subtexture from invalid textureAbortedCode:
terminate called after throwing an instance of 'GG::SubTexture::BadTexture' what(): Attempted to construct subtexture from invalid textureAbortedStatistics: Posted by Skyflare — Tue Dec 24, 2024 9:31 am