AddressSanitizer: access-violation on sqlcipher_extra_shutdown() for statically linked application

With SqlCipher 4.9.0 on calling sqlite3_shutdown() address santizer flags access volation inside sqlcipher_extra_shutdown().

Here are the details.

==65668==ERROR: AddressSanitizer: access-violation on unknown address 0x7ffe7ae6e15a (pc 0x7ffe7ae6e15a bp 0x00ae3954dd40 sp 0x00ae3954dc38 T0)
==65668==The signal is caused by a UNKNOWN memory access.
==65668==WARNING: Failed to use and restart external symbolizer!
#0 0x7ffe7ae6e159 ()
#1 0x7ffdf3fa60d4 in _asan_memcpy+0x2c4 (C:\VS2022\14.42.34433\bin\HostX64\x64\clang_rt.asan_dynamic-x86_64.dll+0x1800460d4)
#2 0x7ff7ea25b42f in xoshiro_randomness C:_code\app\SQLite\sqlite3.c:107745
#3 0x7ff7ea25d35b in sqlcipher_internal_free C:_code\app\SQLite\sqlite3.c:108379
#4 0x7ff7ea25c619 in sqlcipher_extra_shutdown C:_code\app\SQLite\sqlite3.c:108105
#5 0x7ff7ea3e8dd1 in sqlite3_shutdown C:_code\app\SQLite\sqlite3.c:187762

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: access-violation ()
==65668==ABORTING

Hello @Deb - we haven’t been able to reproduce any related issues building SQLCipher 4.9.0 with clang -fsanitize=address. We would need additional information and a working reproduction in order to investigate further. Please provide specific details for reproduction steps, including relevant build information, standalone code that triggers the error, and any CFLAGS in use when building with SQLCipher.