fatal error: runtime: out of memory #647
Comments
|
that was fast! I'll give it a try and an update soon. Thanks in advance! |
|
After some tweaking it seems to be resolved. |
|
I'd like to bring the attention back to this issue. It's still ongoing even with reduced params for argon2 algorithm. |
|
Please provide more derails and a reproducible test case or a memory profile, thank you! |
|
ok I would, but not really an expert on this. So, how do I extract/generate a memory profile? |
|
@aeneasr let me know something |
|
You can create a memory profile by setting |
|
I'm experiencing the same issue. In my case, it happens if I try and use the self-registration functionality in the self-service UI. I have an extremely simple Kratos config (mostly in environment variables): kratos.yml: Environment variables: |
|
Doh. Thanks, @aeneasr - to be perfectly honest, I skipped over that thread because I thought "Argon2? I'm not using that" and didn't realize it was something internal to Kratos. |
This patch adds the new command "hashers argon2 calibrate" which allows one to pick the desired hashing time for password hashing and then chooses the optimal parameters for the hardware the command is running on:
```
$ kratos hashers argon2 calibrate 500ms
Increasing memory to get over 500ms:
took 2.846592732s in try 0
took 6.006488824s in try 1
took 4.42657975s with 4.00GB of memory
[...]
Decreasing iterations to get under 500ms:
took 484.257775ms in try 0
took 488.784192ms in try 1
took 486.534204ms with 3 iterations
Settled on 3 iterations.
{
"memory": 1048576,
"iterations": 3,
"parallelism": 32,
"salt_length": 16,
"key_length": 32
}
```
Closes #723
Closes #572
Closes #647
Describe the bug
Experiencing "runtime out of memory" errors on two running instances.
The affected route seems to be
/self-service/browser/flows/login/strategies/password?request=....One common symptom I find in the logs is the long response time of that route, where values between 10 and >30 secs are common.
The setup is kratos, pg and mailslurper, as this is a development environment.
Reproducing the bug
Hard to say, but here are the logs...
Server logs
Docker Stats
Docker Log Kratos
Server configuration
Expected behavior
No out of memory exception and an acceptable response time (<1sec).
Environment
The text was updated successfully, but these errors were encountered: