I opened a technical blog post and left the tab to read later, only to discover it was choking the browser to death with a sudoku-solving neural network embedded as a proof of concept ballooning to 5GB
-
@0xabad1dea the web was a mistake
@outfrost @0xabad1dea JavaScript was a mistake. My machine, my choice of programs to run on it.
-
@outfrost @0xabad1dea JavaScript was a mistake. My machine, my choice of programs to run on it.
@RogerBW @0xabad1dea are you sure it's just js
-
I opened a technical blog post and left the tab to read later, only to discover it was choking the browser to death with a sudoku-solving neural network embedded as a proof of concept ballooning to 5GB
@0xabad1dea Solving Sudoku with NN using 5G memory is no proof of concept, it is a proof of cluelessness.
For a 5x5 Sudoku you need a FNN with 25 inputs, 3 outputs and about 50 hidden nodes, thus 1400 weights. No recurrency needed as the problem is time invariant. So you'd need about 10kB memory for the network and about 20kB for interops.
Don't blame Javascript. Blame the author...
-
@0xabad1dea Solving Sudoku with NN using 5G memory is no proof of concept, it is a proof of cluelessness.
For a 5x5 Sudoku you need a FNN with 25 inputs, 3 outputs and about 50 hidden nodes, thus 1400 weights. No recurrency needed as the problem is time invariant. So you'd need about 10kB memory for the network and about 20kB for interops.
Don't blame Javascript. Blame the author...
@Amorpheus "ballooned" is a load-bearing word in this post, describing what happens when you leave apps that weren't tested against the conditions of running for three days running for three days
-
@Amorpheus "ballooned" is a load-bearing word in this post, describing what happens when you leave apps that weren't tested against the conditions of running for three days running for three days
@0xabad1dea Sorry for my misconception. Producing such a devastating memory leak with Javascript just blew my mind. I would have to code something like that on evil purpose in order having the garbage collector not to destroy unused references.
-
@0xabad1dea Sorry for my misconception. Producing such a devastating memory leak with Javascript just blew my mind. I would have to code something like that on evil purpose in order having the garbage collector not to destroy unused references.
@Amorpheus it's probably wasm around scipy or something like that.
-
I opened a technical blog post and left the tab to read later, only to discover it was choking the browser to death with a sudoku-solving neural network embedded as a proof of concept ballooning to 5GB
@0xabad1dea doesn't surprise me. lol
-
I opened a technical blog post and left the tab to read later, only to discover it was choking the browser to death with a sudoku-solving neural network embedded as a proof of concept ballooning to 5GB
@0xabad1dea 2026…
-
@Amorpheus it's probably wasm around scipy or something like that.
@0xabad1dea Yeah, you'd have to use native arrays or asm in that sense. Even then, most browsers have a fixed limit on memory and cpu usage.
I state on this because having people disable Javascript really breaks a lot of sites. There are more reasonable countermeasures. Some browsers support crypto mining inhibition. Having a strict cross-origin policy on ajax and ws enabled is essential, too.
I wonder what browser you use, cause 5G really is out of the ordinary limitations, even for wasm.
-
@0xabad1dea Yeah, you'd have to use native arrays or asm in that sense. Even then, most browsers have a fixed limit on memory and cpu usage.
I state on this because having people disable Javascript really breaks a lot of sites. There are more reasonable countermeasures. Some browsers support crypto mining inhibition. Having a strict cross-origin policy on ajax and ws enabled is essential, too.
I wonder what browser you use, cause 5G really is out of the ordinary limitations, even for wasm.
@Amorpheus it’s normal chrome and I’m just reporting the memory usage reported by chrome for the whole tab after noticing the browser nearly died when I switched back to it, and then discovering that a few paragraphs in there are a bunch of NN demos and visualizers
