search

Razish / japp

JA++ server and client modification for Jedi Academy
GNU General Public License v2.0
44 stars 30 forks source link

Fix: adminadd crash #383

Open Blackwolf1337 opened 8 years ago

Blackwolf1337 commented 8 years ago

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.

ensiform commented 8 years ago

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.

Blackwolf1337 commented 8 years ago

@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

ensiform commented 8 years ago

I thought japp had crash dump support in the server. @Razish ?

Blackwolf1337 commented 8 years ago

@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.

Razish commented 8 years ago

There's no log at all? Or is it an empty file? Did you build with no_crashhandler=1 or run with japp_crashHandler 0?

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? Can I get the exact commands + arguments you used to add admins? It may be related.

EDIT: I've just created over 100 admins on a dedicated linux server with no issues.

Blackwolf1337 commented 8 years ago

The crashhandler is implemented and turned on, no log file at all. As I described above.