Software /
code /
prosody-modules
File
mod_log_events_by_memory/README.md @ 6191:94399ad6b5ab
mod_invites_register_api: Use set_password() for password resets
Previously the code relied on the (weird) behaviour of create_user(), which
would update the password for a user account if it already existed. This has
several issues, and we plan to deprecate this behaviour of create_user().
The larger issue is that this route does not trigger the user-password-changed
event, which can be a security problem. For example, it did not disconnect
existing user sessions (this occurs in mod_c2s in response to the event).
Switching to set_password() is the right thing to do.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 06 Feb 2025 10:13:39 +0000 |
parent | 6003:fe081789f7b5 |
line wrap: on
line source
This module compares the memory usage reported by Lua before and after each event and reports it to the log if it exceeds the configuration setting `log_memory_threshold` (in bytes). ``` lua log_memory_threshold = 20*1024 ``` If you are looking to identify memory leaks, please first read [Three kinds of memory leaks](https://blog.nelhage.com/post/three-kinds-of-leaks/). Prosody runs on Lua which uses automatic memory management with garbage collection, so the numbers reported by this module are very likely to be useless for the purpose of identifying memory leaks. Large, but temporary, increases in memory usage can however highlight other kinds of performance problems and sometimes even provide hits for where to look for memory leaks.