-
Notifications
You must be signed in to change notification settings - Fork 30
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
Fix: adminadd crash #383
Comments
A crash dump would be great. The fact that the file is lost is because the crash happens during a file write I believe which can lead to that happening. |
@ensiform as much as I would like to share with you the crash dump, but there is not one. Since it crashes randomly and doesn't create a dump / log |
I thought japp had crash dump support in the server. @Razish ? |
@ensiform It does, but this crash is somehow glitchy. The Crash Dump collector of ja++ won't print it out. You can try by yourself.Normally it puts out a .log file with the assembler code within it. |
There's no log at all? Or is it an empty file? It works by listening for signals from the OS/kernel like SIGSEGV/segmentation fault/"crash" and works from there, it doesn't matter what was executing previously. Was this on a listen server or a separate dedicated server? EDIT: I've just created over 100 admins on a dedicated linux server with no issues. |
The crashhandler is implemented and turned on, no log file at all. As I described above. |
So recently I've tried something stupid. I added +30 Admin Accounts after some more the Server Crashed. No Crash log at all. I don't know if this has to do with the memory allocation, but seem's like. Probably a memory leak I don't know...
-Edit-
Don't forget to backup your admins.json, when trying this out. After a crash your .json will be emptied.
The text was updated successfully, but these errors were encountered: