Skip to content
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

Memory overload, Securly bypass, Questions #40

Open
oChron1c opened this issue Dec 17, 2024 · 0 comments
Open

Memory overload, Securly bypass, Questions #40

oChron1c opened this issue Dec 17, 2024 · 0 comments

Comments

@oChron1c
Copy link

Hi, I hope you've been having a wonderful day so far! I have a lot to talk about and the issues I'm experiencing are complicated, so please hear me out and read the whole thing before responding or clicking off.

I have used this exploit and there are quite a few issues that I'd like to get feedback and support on. So, the first issue is probably the biggest one; my biggest issue is memory overload. So, I'm aware that the exploit spams iframes in a similiar way to LTMEAT flood, (I prefer Andromeda flood though) however the page tells me that the hanging process only takes about a minute. Yet, After hanging, my computer is still exponentially slow and (partially) unresponsive. I don't really understand why the exploit is slowing down my computer 100x, esepecially after I finished hanging Securly. I did check task manager and saw that the exploit page, after hanging, still took up a whopping 33.33% of my memory. I don't why this is, and I have no idea how to fix this or if it is intentional. Either way, though, this issue completely prevents me from using this exploit as it renders my computer useless. Please help.

The next issue is that, after my computer starts working again, (5-10 minutes after hanging) Securly also starts working as well. This might be tied into the previous issue, but it (probably) isn't as complicated so I'm sure that you can give me an answer on this.

Lastly, I'm wondering if I need to kill the extension to have the exploit work. Again, this issue is far less complicated than the first one.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant