-
Notifications
You must be signed in to change notification settings - Fork 72
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
[BUG] Replay Bot Memory Leak? #257
Comments
here are more crashes I already have daily, hope that Olokos fixes them :Kapp: |
@freakexeuLow when you're reffering to me, don't hesitate to mention me just as I did. From what I see at least part of the problem is related to My suggestions first up: Self compile and update momsurffix itself See if it is still crashing, if it still does then disable momentum fix and see how it goes. It would also help if you'd tell us what's going on the server when this bug occurs, after you did the steps mentioned by me above. |
Welcome back Olokos and will you continue working on the SurfTimer or will you leave us again? DHooks is on the last version "DHooks (2.2.0-detours15): Dynamic Hooks" If something like this happens again, I will send the logs here |
I didn't leave at any point, I came back to catch up with stuff and help with current issues. If you want to do some more testing then try to disable momentum fix smx and make sure you are using latest dev code which is commit 22802eb and then enable bots again. |
I too have this memory leak, i think it occurs when the bots break in that infinite loop of starting and stopping within like 1 second |
Does this bug happen all the time for you guys or after a certain time or on certain event? |
As I said, it's the timer. I have 3 servers with the SurfTimer, it just happens sometimes, I can't be on the server 24/7 and check it olokos and I don't think the momentum fix had anything to do with it, it worked with SurfTimer 2.8.5v without problems. So I also said, nothing more comes from you and you let Bara do everything. I think he has less experience in this area than you do, but at least he tried but I am grateful for that. I hope that you will finally fix these problems and don't leave again, it's a big project with certain problems, fluffy has already given his opinion that this doesn't make any sense anymore, so we will continue to support it as the "cksurf" already came with many problems. There are enough people who would continue to test it, but unfortunately, 0 fixes come from you and you just let your team alone. I would also write more about it, but I don't want to cause stress or anything, I'm curious if it continues or if you leave the project as it is. ;) |
I'm not entirely sure why you are trying to make a scene here, I also have my own life and matters that need taking care of, but lets make some things clear. It's not my job, but a hobby to work on surftimer. Each time I come back to start working on surftimer, there's always somebody acting in the exact same way as you are now.
So having more experience means that one has to work on something day and night restlessly? Nice logic.
I've had bots running on the server even if it's empty since my last message and there were no crashes so far, with momentum fix aswell, so I hope you can bring something valuable into this issue, apart from trying to make an unnecessary and pointless drama. Saying
at the end is not magically going to make the stress go away, but your behavior surely does demotivate. I really hope you are going to bring something valuable in your next message, so we can resolve the issue, if it actually even still exists. |
|
Not sure why you're straight up lying at this point, but lets clear this one up.
It is solved because:
Every member of the surftimer organization could've done this aswell, since I transferred the ownership quite some time ago now. But nobody did, maybe out of respect, maybe for some other reason, but it was me who did this.
If your point is that I should quit completely on this project and move on, then you're doing it right, but I am done with your nonsense. From now on I'll ignore anything you write unless it's actually of any value to the project or its issues. As I just wasted way too much time on responding to your attacks on me. Provide fresh logs generated with surftimer up to 22802eb commit or go away. |
Describe the bug
Since the 1.10 there are more crashes and at the end something about replay. When exactly all this comes is written there, I am already sleeping at this time.
Full Error Log
Link: https://pastebin.com/NBP0GgBq
Plugin List
SurfTimer 1.10
MomSurfFix 1.1.3
The text was updated successfully, but these errors were encountered: