You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The KtxUtility class is a thin convenience layer around the BinomialLLC Basis Universal encoder. It mainly offers that function convertImageData, where the caller can throw in some arbitrary image data, and receive the resulting KTX image data. This is hiding all the nitty-gritty bits of (compiling!)/loading/initializing/configuring the underlying WASM module.
When calling this method many (many) times, it eventually causes a RuntimeError to be thrown from the WASM part:
RuntimeError: Aborted(). Build with -sASSERTIONS for more info.
(+ some stack trace into the WASM). The tooling and debugging possibilities around WASM are ... ... ... have a lot of room for improvement. But the observed behavior is a hint at ~"some sort of memory leak".
The WASM module has a delete() function. The documentation of this function is:
/*
* Just kidding. It is not documented...
*/
But calling this function at the right place and time might resolve this issue.
The text was updated successfully, but these errors were encountered:
The
KtxUtility
class is a thin convenience layer around the BinomialLLC Basis Universal encoder. It mainly offers that functionconvertImageData
, where the caller can throw in some arbitrary image data, and receive the resulting KTX image data. This is hiding all the nitty-gritty bits of (compiling!)/loading/initializing/configuring the underlying WASM module.When calling this method many (many) times, it eventually causes a RuntimeError to be thrown from the WASM part:
(+ some stack trace into the WASM). The tooling and debugging possibilities around WASM are ... ... ... have a lot of room for improvement. But the observed behavior is a hint at ~"some sort of memory leak".
The WASM module has a
delete()
function. The documentation of this function is:But calling this function at the right place and time might resolve this issue.
The text was updated successfully, but these errors were encountered: