PerimeterX / restringer

A Javascript Deobfuscator

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

dont know if this is normal or what?

xmoufyy opened this issue · comments

so i always get stuck on resolveAugmentedFunctionWrappedArrayReplacements for hours on end and accidently closed it once but also my file is 48000kb and very long so i wanna know if its normal or a performance issue

the memor usage also stays the same while its doing it and slowly goes down every few minutes

Yeah it seems this method causes trouble sometimes. It should definitely be refactored to avoid this issue.
You can try and comment it out from the restringer.js file (line 136) to avoid the issue for now

Yeah it seems this method causes trouble sometimes. It should definitely be refactored to avoid this issue. You can try and comment it out from the restringer.js file (line 136) to avoid the issue for now

yeah thanks it worked but also got this is this normal or what sorry for the questions im new to this
image

there is a lot and when it was done said nothing was deobfuscated dont know if u want the code to what i was deob'ing to try and update obfuscator detector or whatever just lmk

What you're seeing is normal when showing log level DEBUG. You can ignore it since it just means a piece of code could not be evaluated. That happens a lot and is expected behavior whether anything was deobfuscated or not.