aboutsummaryrefslogtreecommitdiff
path: root/ext/wasm/api/sqlite3-vfs-opfs-sahpool.c-pp.js
diff options
context:
space:
mode:
authorstephan <stephan@noemail.net>2023-08-04 08:45:25 +0000
committerstephan <stephan@noemail.net>2023-08-04 08:45:25 +0000
commita24769454e2ddd05d543d9b3cf20401cf6c43bdb (patch)
treeb17826baca838c53a112edaf544bf6b23088ffd8 /ext/wasm/api/sqlite3-vfs-opfs-sahpool.c-pp.js
parent444424dab8c5fff24256ab32f0279e3e0b841961 (diff)
downloadsqlite-a24769454e2ddd05d543d9b3cf20401cf6c43bdb.tar.gz
sqlite-a24769454e2ddd05d543d9b3cf20401cf6c43bdb.zip
Resolve the timing/ordering issue of a JS-to-WASM-converted xDestroy() function being uninstalled from WASM right before the underlying native call tries to call it. This has been a long-unnoticed bug which appears only when removing such functions or replacing them.
FossilOrigin-Name: 031c9a76b6ad1572e7a88f4d2d62f206b0d37bd1170e2c8a24248c5ec628f2f5
Diffstat (limited to 'ext/wasm/api/sqlite3-vfs-opfs-sahpool.c-pp.js')
0 files changed, 0 insertions, 0 deletions