From 3ab2474fa0b3bc8a09279d3aa33f0651522a420d Mon Sep 17 00:00:00 2001 From: Vladimir Marko Date: Thu, 17 Mar 2022 07:11:11 +0000 Subject: Use correct min/max load factor in intern/class table. Propagate the min/max load factor that was initially set based on low memory mode flag to new internal sets. And clean up some dead code related to image writing. Test: m test-art-host-gtest Test: testrunner.py --host --optimizing Change-Id: Id13c8a4833e93458a3f5eed22dc69431311211b7 --- runtime/class_table.cc | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'runtime/class_table.cc') diff --git a/runtime/class_table.cc b/runtime/class_table.cc index 03921a132a..bd5d38f80d 100644 --- a/runtime/class_table.cc +++ b/runtime/class_table.cc @@ -30,7 +30,11 @@ ClassTable::ClassTable() : lock_("Class loader classes", kClassLoaderClassesLock void ClassTable::FreezeSnapshot() { WriterMutexLock mu(Thread::Current(), lock_); - classes_.push_back(ClassSet()); + // Propagate the min/max load factor from the old active set. + DCHECK(!classes_.empty()); + const ClassSet& last_set = classes_.back(); + ClassSet new_set(last_set.GetMinLoadFactor(), last_set.GetMaxLoadFactor()); + classes_.push_back(std::move(new_set)); } ObjPtr ClassTable::UpdateClass(const char* descriptor, -- cgit v1.2.3-59-g8ed1b