Correct cpu_usage calculation when more than one signature

eosiosg · Aug 27, 2019 · 007ef41 · 007ef41
1 parent 885ef13
commit 007ef41
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/libraries/chain/transaction.cpp b/libraries/chain/transaction.cpp
@@ -120,7 +120,7 @@ fc::microseconds transaction::get_signature_keys( const vector<signature_type>&
       if( it == recovery_cache.get<by_sig>().end() || it->trx_id != tid ) {
          lock.unlock();
          recov = public_key_type( sig, digest );
-         fc::microseconds cpu_usage = fc::time_point::now() - start;
+         fc::microseconds cpu_usage = fc::time_point::now() - start - sig_cpu_usage;
          lock.lock();
          recovery_cache.emplace_back( cached_pub_key{tid, recov, sig, cpu_usage} ); //could fail on dup signatures; not a problem
          sig_cpu_usage += cpu_usage;