Zhichao Cao 0933360644 Fix the potential memory leak in trace_replay (#5955) ... Summary: In the previous PR https://github.com/facebook/rocksdb/issues/5934 , in the while loop, if/else if is used without ending with else to free the object referenced by ra, it might cause potential memory leak (warning during compiling). Fix it by changing the last "else if" to "else". Pull Request resolved: https://github.com/facebook/rocksdb/pull/5955 Test Plan: pass make asan check, pass the USE_CLANG=1 TEST_TMPDIR=/dev/shm/rocksdb OPT=-g make -j64 analyze. Differential Revision: D18071612 Pulled By: zhichao-cao fbshipit-source-id: 51c00023d0c97c2921507254329aed55d56e1786		2019-10-22 16:39:46 -07:00
..
block_cache_tracer.cc	Block cache analyzer: Support reading from human readable trace file. (#5679)	2019-08-09 13:13:54 -07:00
block_cache_tracer.h	Block cache analyzer: Support reading from human readable trace file. (#5679)	2019-08-09 13:13:54 -07:00
block_cache_tracer_test.cc	Block cache analyzer: Support reading from human readable trace file. (#5679)	2019-08-09 13:13:54 -07:00
trace_replay.cc	Fix the potential memory leak in trace_replay (#5955)	2019-10-22 16:39:46 -07:00
trace_replay.h	Enable trace_replay with multi-threads (#5934)	2019-10-18 14:13:50 -07:00