Hi,
> Just in case if someone will be looking for solution - I've managed to
> eliminate all the sensitive data from memory on closing particular QML
> screen without sacrificing existing architecture. The secret is pretty
> simple: just avoid situations when QString-s gets copied into JS
> string
Just in case if someone will be looking for solution - I've managed to
eliminate all the sensitive data from memory on closing particular QML
screen without sacrificing existing architecture. The secret is pretty
simple: just avoid situations when QString-s gets copied into JS
strings:
1. Do not u
