https://github.com/lldap/lldap logo
Powered by
flowbot - Hi, just recently, the User List on m...
# troubleshooting
f
Hi, just recently, the User List on my server stopped loading and browser console shows an error:
Copy code
panicked at /build/rustc-1.79.0-src/vendor/dlmalloc-0.2.6/src/dlmalloc.rs:1198:13:
assertion failed: psize <= size + max_overhead

Stack:

Error
    at imports.wbg.__wbg_new_abda76e883ba8a5f (https://auth.bendlas.net/pkg/lldap_app.js:478:21)
    at https://auth.bendlas.net/pkg/lldap_app_bg.wasm:wasm-function[1264]:0x145f98
    at https://auth.bendlas.net/pkg/lldap_app_bg.wasm:wasm-function[2193]:0x15fffc
    at https://auth.bendlas.net/pkg/lldap_app_bg.wasm:wasm-function[2103]:0x15e8b7
    at https://auth.bendlas.net/pkg/lldap_app_bg.wasm:wasm-function[1733]:0x156f83
    at https://auth.bendlas.net/pkg/lldap_app_bg.wasm:wasm-function[157]:0x3d048
    at https://auth.bendlas.net/pkg/lldap_app_bg.wasm:wasm-function[765]:0x112d31
    at https://auth.bendlas.net/pkg/lldap_app_bg.wasm:wasm-function[2472]:0x166ec5
    at __wbg_adapter_36 (https://auth.bendlas.net/pkg/lldap_app.js:240:10)
    at real (https://auth.bendlas.net/pkg/lldap_app.js:201:20)
Groups list still works. I've tried clearing site data. I'm on 0.5.0
a
message has been deleted
n
Do you have, by any chance, a lot of users?
(how many users do you have? Ballpark)
Context: the error looks like out-of-memory in the wasm frontend, probably due to trying to handle more components than is reasonable in one page. The obvious answer to that would be paging, which LLDAP doesn't support out of simplicity, as it was made for small self-hosted servers where you know all the users (more or less)
f
Not many. 6 users to be exact. I can DM you the user list it it would help. Also, it used to work until recently. I'm suspecting an issue with the wasm toolchain.
n
There hasn't been much activity on the frontend part recently (or the backend, fwiw), to the despair of all those waiting for a stable release of 0.5 😄
Are you on latest docker, or a dated image? Or a self-built checkout?
f
I'm using the NixOS build (for which I'm incidentally also the maintainer). I'm also running the very same build on a few friends' machines, none of which show the behavior, so maybe it's not the wasm chain but rather the data ...
btw since we're talking: we'll have to update everything to rust 1.80 in the coming days. are there any known issues with that? I'll keep you posted how it goes and fingers crossed it might also resolve my issue ...
n
Do any of your users have a huge jpeg avatar photo?
Feel free to send a PR updating the rust version of the various dockerfiles. I don't expect issues since clippy uses nightly, and it compiles without warnings
f
Just one person has an avatar at all, and 36K doesn't seem huge:
Copy code
sql
SELECT length(user_attribute_value) FROM user_attributes
WHERE user_attribute_name = 'avatar'
Copy code
"length"
35832
n
Yeah, that doesn't seem that bad
Is it an SQLite DB? Or can you easily clone the DB? Can you try spinning up a test instance and deleting users until it works, to find the problematic user?
f
postgres .. but yeah, guess I can do that ...
wondering if it has to do with unicode characters in user names
n
It shouldn't, that's been ironed out
f
It's indeed unicode: I can reproduce it by setting a user's first name to "João" and I can fix it by as little as rewriting that "ã" to an "a"
I'll try a couple of things, including updating toolchain (because we have to anyway) and maybe running latest commit, let you know how it goes ...
when you say "ironed out", can you remember what has been done? just so I know what to look out for ...
n
Sorry, that's been a while
I'll try to have a look in the next few days
f
OK, a few more datapoints for you:
bad news first: I can reproduce the error from a source checkout on main.
I could get lldap to build on rust 1.80, however, the server only builds with a 
cargo update
, while the client only builds without it. I'll open an issue for this ..
aand the one that this thread is about: https://github.com/lldap/lldap/issues/946
n
Thanks!
PreviousNext
Powered by