3 ms·
Here is the one: Sciter renders: https://sciter.com/temp/sciter-analog-clock.png https://sciter.com/temp/sciter-analog-clock.png - it takes 50 Mb of memory for
by c-smile 9y ago
Here is the one:
Sciter renders: https://sciter.com/temp/sciter-analog-clock.png https://sciter.com/temp/sciter-analog-clock.png - it takes 50 Mb of memory for the whole process.
This clock sample ( https://github.com/c-smile/sciter-sdk/blob/master/samples/graphics/analog-clock.htm https://github.com/c-smile/sciter-sdk/blob/master/samples/gr... ) is a port of Mozilla's clock : https://codepen.io/anon/pen/vJpqOY https://codepen.io/anon/pen/vJpqOY
Chrome needs 6 separate processes to run this sample with total memory consumption of 575 Mb.
- bonyt 9y agoI fired up Windows 2.03 in DOSBox, with its clock app, available on archive.org[1], and it took up 60.1 MB. This is fun! I think the OS would run fine (at least, enough for the clock) with as little as 512K of ram[2]. Screenshot: https://i.imgur.com/09xjyPs.png https://i.imgur.com/09xjyPs.png [1]: https://archive.org/details/msdos_win2_03 https://archive.org/details/msdos_win2_03 [2]: https://support.microsoft.com/en-us/help/32905/windows-version-history https://support.microsoft.com/en-us/help/32905/windows-versi... ("512K of memory or greater" for 2.03).
- c-smile 9y agoIf you have screen of size 640*480 and rendering without AA then you can render by CPU. Otherwise, with modern hardware and 200 ppi monitors you will need GPU rendering with the whole infrastructure.
- benjarrell 9y agoWhat is that properties window from? That is not the properties window I am used to seeing.
- c-smile 9y agoThat's Process Explorer by Mark Russinovich