-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Mosquitto v 2.0.17 segfault on debian bookworm and huge CPU usage #2881
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I have the same issue with 2.0.16:
All null dereference in libc, which usually indicates some kind of printf bug, or feeding
I've gotten the crashes after 10 and 30 minutes running time. I did not have the opportunity to take the time with a debug build and a debugger. |
Ha, my system actually still had a core handler set, so I have core dumps of it. The (slightly redacted) backtrace, of a release build unfortunately, is:
This was done with a binary compiled from source from tag The |
Thanks for the stacktrace. Will try to take a look into it today. The only strcmp in this line is comparison of the id between the context of existing subscription and the context currently received subscription. But the id representing the clientid of the session should never be NULL. |
I also sent some details to Roger per request. Persistence is enabled. Mosquitto started crashing after having been restarted into 2.0.16, after which I reverted to 2.0.15 and it was stable again. The restart process was shutting down 2.0.15, which saved a 700 MB mosquitto.db, which is then loaded. I have two core dumps, both have virtually the exact same stack trace, including the fact that libwebsocket was involved. |
After I did upgrade to version 2.0.17 on my debian bookworm I am gettting segaults and cpu usage of mosquitto is huge.
The text was updated successfully, but these errors were encountered: