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
Poking around I found talk of setting total memory. I found this even works:
window.sodium = {
totalMemory: something,
};
However it causes a Abort({}) error as described in #132
I am hoping to get a more authoritative answer if changing the memory is possible or not. I get the sense that it isn't a documented feature and not quite ready but wanted to check. It makes the pw_hash feature effectively unusable without sumo (but I don't need sumo now that pw_hash is in non-sumo). Is there any workaround? I'm guessing I could compile myself to set ram instead of doing it in JS?
The text was updated successfully, but these errors were encountered:
Exception in thread Thread-3:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 754, in run
self.__target(*self.__args, **self.__kwargs)
File "/usr/lib/python2.7/multiprocessing/pool.py", line 392, in _handle_results
task = get()
TypeError: __init__() takes at least 3 arguments (1 given)
Ubuntu 17.10. I tried building libsodium (not js) but get the same error on make check.
Poking around I found talk of setting total memory. I found this even works:
However it causes a Abort({}) error as described in #132
I am hoping to get a more authoritative answer if changing the memory is possible or not. I get the sense that it isn't a documented feature and not quite ready but wanted to check. It makes the pw_hash feature effectively unusable without sumo (but I don't need sumo now that pw_hash is in non-sumo). Is there any workaround? I'm guessing I could compile myself to set ram instead of doing it in JS?
The text was updated successfully, but these errors were encountered: