Search Issue Tracker
Active
Under Consideration for 6000.0.X
Votes
0
Found in
6000.0.51f1
6000.1.7f1
Issue ID
UUM-109218
Regression
No
Crash on core::base_hash_set when building a specific project
Steps to reproduce:
1. Open the “user’s attached project”
2. Open the “Main Menu” Scene
3. Go to “Gilligames/Build/All“ through the Main Menu
4. Repeat step 3 if both builds for Mac and Windows succeed
5. Observe crash
Reproducible with versions: 6000.0.51f1, 6000.1.7f1
Couldn’t test with versions: 2021.3.52f1, 2022.3.63f1, 6000.2.0b6 (due to compiler errors)
Reproducible on: macOS 15.5 (M1 Max)
Not reproducible on: no other environment tested
Notes:
- The crash is inconsistent, it can take a few times to build until the crash occurs
- The crash might occur both while building for Mac and Windows platforms
First few lines of StackTrace:
{noformat}#0 0x0000010514336c in core::base_hash_set<core::pair<core::basic_string<char, core::StringStorageDefault<char>> const, keywords::LocalKeyword, true>, core::hash_pair<core::hash<core::basic_string_ref<char>>, core::basic_string<char, core::StringStorageDefault<char>>>, core::equal_pair<std::__1::equal_to<core::basic_string_ref<char>>, core::basic_string<char, core::StringStorageDefault<char>>>>::node* core::base_hash_set<core::pair<core::basic_string<char, core::StringStorageDefault<char>> const, keywords::LocalKeyword, true>, core::hash_pair<core::hash<core::basic_string_ref<char>>, core::basic_string<char, core::StringStorageDefault<char>>>, core::equal_pair<std::__1::equal_to<core::basic_string_ref<char>>, core::basic_string<char, core::StringStorageDefault<char>>>>::lookup<core::basic_string<char, core::StringStorageDefault<char>>, core::equal_pair<std::__1::equal_to<core::basic_string_ref<char>>, core::basic_string<char, core::StringStorageDefault<char>>>>(core::basic_string<char, core::StringStorageDefault<char>> const&, core::equal_pair<std::__1::equal_to<core::basic_string_ref<char>>, core::basic_string<char, core::StringStorageDefault<char>>> const&) const
#1 0x0000010513f4cc in keywords::LocalSpace::Find(core::basic_string<char, core::StringStorageDefault<char>> const&) const
#2 0x0000010513f3ac in keywords::KeywordRemap::Init(keywords::LocalSpace const&, keywords::LocalSpace const&)
#3 0x0000010515ece0 in ShaderLab::IntShader::ResolveFallback(ShaderLab::SerializedShader const&, Shader, core::vector<PPtr<Shader>, core::allocator<PPtr<Shader>, 0ul>>&, bool)
#4 0x000001050f1ea0 in ShaderLab::IntShader::CreateFromSerializedShaderMainThread(ShaderLab::IntShader, ShaderLab::SerializedShader const&, core::vector<PPtr<Shader>, core::allocator<PPtr<Shader>, 0ul>>&, bool, Shader*){noformat}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Add comment