Page 1 of 1

Unresponsive Script Warnings

Posted: Thu Aug 18, 2011 9:22 am
by Pradeep K
First of all Thanks for the great tool. It really helps to analyze the malicious contents for research.

While using the tool for some URL's which has heavily obfuscated contents I've observed that it throws warning,

"A script on this page may be busy, or it mau have stopped responding
You can stop the script now, or you can continue to see if the script will
complete

Script: chrome://jsdeobfuscator/content/jsdeobfuscator.js:312 /

Script: Script: chrome://jsdeobfuscator/content/jsdeobfuscator.js:167"

Extension version : 1.5.7

The dialogue box gives you two options either to "Stop script" or "Continue". Stopping the script results into accurate
de-obfuscated contents.

Firefox dev guide : http://kb.mozillazine.org/Unresponsive_Script_Error. Tried with increasing dom.max_script_run_time/dom.max_chrome_script_run_time
but in this case sometimes firefox hangs.

Is there anyway to suppress these warnings in the extension itself?

Pradeep

Re: Unresponsive Script Warnings

Posted: Tue Aug 23, 2011 4:57 pm
by Wladimir Palant
Sounds like JS Deobfuscator is adding massive amounts of text to the output window. Suppressing the warning should be the wrong course of action, it would be better to prevent this from slowing things down. Main question being: how to improve the performance here. Maybe it would be better to display text delayed, in batches...

Re: Unresponsive Script Warnings

Posted: Thu Aug 25, 2011 7:11 am
by PradeepK
Yes definitely that can improve it. Can you please try to find workaround about this issue. I'll happy to provide contents which causes this issue.

Re: Unresponsive Script Warnings

Posted: Fri Mar 25, 2016 12:08 pm
by makaijohn9
Me too was suffering with the same problem. Thanks for suggesting some points to solve this issue.

Re: Unresponsive Script Warnings

Posted: Sat Mar 26, 2016 5:14 am
by smed79
makaijohn9 wrote:Me too was suffering with the same problem. Thanks for suggesting some points to solve this issue.
Five years later?

Refresh your brewser and reinstall adblock plus.
ff - https://support.mozilla.org/kb/reset-fi ... t-problems
ch - https://support.google.com/chrome/answer/3296214
abp - https://adblockplus.org/