You shouldn't see this.
https://twitter.com/juju2143/status/793475099450077184
EDIT: Broken image in Firefox. As far as I can see, it just does something weird and unexpected in Chrome.
Edited the db to get in here. Nice find. :P
Did you put the BADs on the end on purpose? :P
Quote from: aeTIos on November 01, 2016, 06:11:24 PM
Did you put the BADs on the end on purpose? :P
Lol, no.
echo -n "GIF89a\xE7\x5E\x52\x56\x00\x00\x00\x2C\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01\x00;" | base64
Weird. Is this related to the http://a/&&30%30 crash bug that existed a few years ago?
When to juju's link, chrome didn't crash :(
(http://data:image/gif;base64,R0lGODlh515SVgAAACwAAAAAAAAAAAABADs=)
the first time I opened the topic I got an errof for the page.
But after the first comment was posted I was able to open it without any problems
Quote from: WholeWheatBagels on November 01, 2016, 08:29:41 PM
Weird. Is this related to the http://a/&&30%30 crash bug that existed a few years ago?
Dunno, maybe.
Quote from: p2 on November 01, 2016, 11:51:02 PM
the first time I opened the topic I got an errof for the page.
But after the first comment was posted I was able to open it without any problems
@Streetwalrus moved it to a link.
Now that I go back and watch the video about that URL I realize its different.
The video if anyone is interested
https://www.youtube.com/watch?v=0fw5Cyh21TE
Still cool though!
Yeah, well, Chrome would crash the same, the tab insta-crashes as soon as you open it, but the problem is probably different. Maybe something with the GIF parser that chokes with so much pixels. As I tested, it works with 2^29 minus a few thousand pixels, but minus 2, nope. 2^29 and more, it won't bother render it.
firefox is neat
plus
it only uses one thread for all its windows/tabs which i like a lot :thumbsup:
Quote from: kotu on November 02, 2016, 01:16:27 AM
it only uses one thread for all its windows/tabs which i like a lot :thumbsup:
This sucks so hard :(
I use firefox as my main browser but it is slow as hell :(
YEah by using 1 thread I assume that if one tab crashes then you need to close the entire browser, right?
Also I don't think I'll click the URL in the first post, in case. :P
Yeah, the whole point of a multi-process browser is that if one tab crashes, it won't crash the whole browser.
i know
Cool !
Somehow, that reminds me how it's possible to insert javascript code in gifs.
Do run this :
<html><head>
<img src="microbee.gif">
<script src="microbee.gif">
</script>
</head><body></body></html>
And download this pict.
(https://gameblabla.nl/img/microbee.gif)
It should work on Firefox.
Wow, I didn't know this. Nice trickif it'scross-browser compatible. :)
This is how it works apparently. https://quadhead.de/storing-javascript-code-in-gif-images/
It shouldn't be harmful, considering you need the ability to inject a <script> tag into the page.
Hm I see. I am curious about if it works in IE6 :P
Oooh, nice.
Quote from: DJ Omnimaga on November 02, 2016, 04:31:31 PM
Hm I see. I am curious about if it works in IE6 :P
IE6 doesn't even need such a gif to crash while loading a page :P
Quote from: ben_g on November 02, 2016, 05:23:45 PM
Quote from: DJ Omnimaga on November 02, 2016, 04:31:31 PM
Hm I see. I am curious about if it works in IE6 :P
IE6 doesn't even need such a gif to crash while loading a page :P
IE6 crashed much less than the 2005-07 versions of Firefox, though :P (version 1.05 until the end of 2.x). I had to CTRL+Alt+Del every 5 minute or so when using Firefox.
There was also the bug that caused Firefox to use 6 times more resources than Crysis at maxed out settings when a link was broken from time to time. Firefox would just freeze and make the entire computer lag like crazy for about 30 seconds before the Page cannot be found/loaded screen appeared.
Anyway I clicked the first post link in Opera and the tab just said out of memory after freezing for a second. To be honest, I don't like data images because they're hard to share (since the URL is so long and often won't fit in the address bar)