Brian Carpenter [:geeknik] Reporter
	Description • 6 years ago

While fuzzing cjpeg I discovered a jpeg that would trigger an immediate increase in Firefox 59, 60 and Nightly (build ID 20180516100125) memory usage from around 500MB to the system maximum before the process is killed. The only thing I could find in the browser console were these messages:

Corrupt JPEG data: 131 extraneous bytes before marker 0xda
Corrupt JPEG data: 131 extraneous bytes before marker 0xda

	Daniel Veditz [:dveditz]
	Comment 2 • 6 years ago

On Mac (variety of Release and Nightly versions) the memory seems to cap out at around 12GB and doesn't get killed, although the CPU keeps churning so I'm not sure what it's doing exactly. With e10s it's easy to close the affected tab, and if it dies not that harmful to the rest of the browser. Or are you seeing something different, like killing the parent process, too?

	Brian Carpenter [:geeknik] Reporter
	Comment 3 • 6 years ago

After churning @ 100% CPU for 2m35.4seconds on a Debian 9.3 VM assigned 4GB of RAM and 4GB of swap, the entire browser is killed by the OS.

	Kent Ross
	Comment 4 • 6 years ago

On my machine, it very quickly allocates ~12 thousand megabytes, thinks for about 35 seconds, then displays a mid-gray square image zoomed out, with native dimensions of 65395x65395 pixels. With 24 bit RGB encoding this image is about 12 gigabytes of bitmap data, which explains the memory usage.

	Timothy Nikkel (:tnikkel)
	Comment 5 • 6 years ago

Without looking into this file specifically I would guess this is a dupe of bug 1277397.