Search Issue Tracker

Won't Fix

Votes

2

Found in

2021.3.33f1

2022.3.16f1

Issue ID

UUM-59504

Regression

No

Crash on POParser::NextEntry when importing a .po file with a syntax error

-

Reproduction steps:
1. Open the attached project “CrashRepro”

Expected result: A warning is thrown “Importer(LocalizationImporter) generated inconsistent result for asset”
Actual result: The Editor crashes

Reproducible with: 2021.3.33f1, 2022.3.16f1, 2023.1.0a22
Not reproducible with: 2023.2.4f1, 2023.3.0b1
Fixed in: 2023.1.0a23

Reproducible on: macOS 14.0 (M1 Max), Windows 10
Not reproducible on: No other environment tested

First few lines of the stack trace:
#0 0x00000188099870 in _platform_memmove
#1 0x0000010180b6f0 in POParser::NextEntry()
#2 0x000001026cdf44 in LocalizationImporter::ImportStringTableFromPOFile(core::basic_string<char, core::StringStorageDefault<char>> const&, StringTable&, core::basic_string<char, core::StringStorageDefault<char>>&)
#3 0x000001026d1f90 in LocalizationImporter::GenerateAssetData(AssetImportContext&)
#4 0x0000010244ed40 in ImportToObjects(core::basic_string<char, core::StringStorageDefault<char>> const&, core::hash_map<AssetDatabase::ImporterID, ImporterInfo, core::hashAssetDatabase::ImporterID, std::__1::equal_toAssetDatabase::ImporterID> const&, dynamic_array<PostprocessorInfo, 0ul> const&, AssetResolveTracker const&, ImportAssetInputs const&, ImportAssetOutputs&, IImportProgress)
#5 0x0000010244debc in ImportAsset(core::hash_map<AssetDatabase::ImporterID, ImporterInfo, core::hashAssetDatabase::ImporterID, std::__1::equal_toAssetDatabase::ImporterID> const&, dynamic_array<PostprocessorInfo, 0ul> const&, AssetResolveTracker const&, ImportAssetInputs const&, ImportAssetOutputs&, IImportProgress
)

  1. Resolution Note:

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.