1575009 - Firefox Crash After A Simple Obfuscation Javascript

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[Marvel Gulane]

Attachment: shit.png

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0

Steps to reproduce:

I opened http://obfuscator.io/ to obfuscate javascript code for security purposes.
Coppied the code into my sublime text 3 for testing.

REF_CODE:(https://pastebin.com/5HDS584z).

Aside from this based in my research Firefox Browser is still vulnerable in
'Browser Reaper Code'.

REF_CODE:(https://pastebin.com/xkSYN2kS)

Actual results:

After 4 cycle of restart while developing my website it slowly eat a lot of RAM & CPU which lead to crash the browser and not being able to operate.
Possible and vulnerable for memory leakage.

Expected results:

Different method but same affected area the ipc_channel

Logs:
[Parent 11606, Gecko_IOThread] WARNING: pipe error (91): Connection reset by peer: file /build/firefox-fvtOIe/firefox-64.0+linuxmint2+tessa/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 363

Degrading performance and lead from browser to Operating System crash, luckily not causing any Kernel Panic. I tried the test in phone, but it just close then opening it again all seem well and back to normal.

Comment 1

[Daniel Veditz [:dveditz]]

See also https://www.reaperbugs.com/index

Comment 2

[Johann Hofmann [:johannh]]

So that "reaper" thingy is just a dupe of bug 1438214 and I have no idea what the first one could be. The code is way too obfuscated. Unless you can provide further details as to what exactly is causing the DOS I think we'll have to close this as INCOMPLETE.

Comment 3

[Raluca Popovici, Desktop QA]

Due to the lack of response I will close this bug. Please feel free to reopen it if you managed to reproduce it again and provide further details as to what exactly is causing the DOS.