Leaksanitizer detected memory leak with Tor Tor 0.4.6.1-alpha-dev (git-769d54c5)

I hit a memory leak with the latest tor code from master when using it in Tor Browser. No special usage, no bridges. Just normal browsing in a bunch of tabs and closing the browser after it had been running a full day:

Direct leak of 392 byte(s) in 7 object(s) allocated from:
    #0 0x7f77ac8bae8f in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:145
    #1 0x56288c6b1778 in tor_malloc_ ../src/lib/malloc/malloc.c:45
    #2 0x56288c6b1810 in tor_malloc_zero_ ../src/lib/malloc/malloc.c:71
    #3 0x56288c89354d in cache_client_desc_new ../src/feature/hs/hs_cache.c:460
    #4 0x56288c89354d in hs_cache_store_as_client ../src/feature/hs/hs_cache.c:873
    #5 0x56288c8a2dd5 in client_dir_fetch_200 ../src/feature/hs/hs_client.c:1463
    #6 0x56288c8a2dd5 in hs_client_dir_fetch_done ../src/feature/hs/hs_client.c:2379
    #7 0x56288c834fa8 in handle_response_fetch_hsdesc_v3 ../src/feature/dirclient/dirclient.c:2721
    #8 0x56288c834fa8 in connection_dir_client_reached_eof ../src/feature/dirclient/dirclient.c:2139
    #9 0x56288c834fa8 in connection_dir_reached_eof ../src/feature/dirclient/dirclient.c:2787
    #10 0x56288c7d1ff1 in connection_reached_eof ../src/core/mainloop/connection.c:5243
    #11 0x56288c7d1ff1 in connection_handle_read_impl ../src/core/mainloop/connection.c:4014
    #12 0x56288c58c240 in conn_read_callback ../src/core/mainloop/mainloop.c:891
    #13 0x7f77ac47c22e  (TorBrowser/Tor/libevent-2.1.so.7+0x2322e)

I am attaching the whole LeakSanitizer output, too.