3 ms·

It crashes Firefox 66.0.3 (64-bit) on Windows 10.0.17763.437. https://crash-stats.mozilla.org/report/index/7d1ca3eb-2d06-43af-a83b-d7e510190421 https://crash-st

• jniedrauer 8y ago
  Works great in Firefox 68.0a1 on Fedora 29 with the HTC Vive front-facing camera.
• y0ghur7_xxx 8y ago
  Works fine on Firefox 66.0.3 (64-bit) on Linux.
• close04 8y ago
  Tested on 66.0.3 on a fully updated Windows 10 (64bit all around) and it works fine.
• MagicPropmaker 8y ago
  If it crashes it, there may be an attack vector here!
  • wybiral 8y ago
    If you really want to crash a Firefox browser without JS, there's this: https://fan-pages.herokuapp.com/ https://fan-pages.herokuapp.com/ It basically keeps sending iframe's with data URL's for download, see code: https://github.com/wybiral/crash https://github.com/wybiral/crash On Chrome it blocks request popups after the first but FF usually crashes (even Tor Browser). The interesting thing about this is that you can keep the connection open as long as you want and then send the iframes on command.
    • chipperyman573 8y ago
      >The interesting thing about this is that you can keep the connection open as long as you want and then send the iframes on command. What do you mean?
      • wybiral 8y ago
        If I'm operating the server I can keep the connection open to your browser and wait until sending the iframes to crash you. So combined with other tracking techniques (to tell if a tab is still open) you can crash their browser and see which other tabs close.
• cpeterso 8y ago
  Good news! That crash (RGB24ToARGBRow_SSSE3) is fixed in Firefox 67 Beta, which will be released on May 14: https://bugzilla.mozilla.org/show_bug.cgi?id=1539220 https://bugzilla.mozilla.org/show_bug.cgi?id=1539220