github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
nwc10 good *, #moarvm 05:23
nine Good morning! 06:25
jnthn morning o/ 09:33
nwc10 \o
The XBox "thing" referenced some weeks ago was xboxdevwiki.net/17_Mistakes_Micros...ity_System and www.youtube.com/watch?v=9NqLljaHc80 09:59
That talk *is* actually watchable (and fun and worth it) even if the start gives some very bad vibes (240p, just one camera from the back and unclear where the microphone is) 10:00
timotimo media.ccc.de/v/22C3-559-en-xbox_hacking this could very well be better 12:15
same person presenting the xbox part as in the google tech talk, with a bonus xbox 360 part by another person 12:16
what on earth, this is also 240p 12:17
nwc10 xboxdevwiki.net/17_Mistakes_Micros...ity_System doesn't link to that, but to the YouTube, probably the same. The other link is described as: Another recording of a slightly updated talk is available here: YouTube: Deconstructing The Xbox Security System
I haven't watched both to figure out what the "slightly updated" meant
timotimo: I forget which conference it was, where Tim Bunce tried the projector, and said roughly "Wow, this thing can actually match the resulotion of my laptop" 12:18
timotimo :D
nwc10 and that was some years ago. Prior to that, we were not living in the future 12:19
the most evil thing that *I* was told about beamers was that they would *claim* to support 1024x768 (or whatever it is) but actually downscale to about 900xsomethi9ng
and produce fuzzy crap
whereas forcing the laptop to talk 800x600 to the beamer would make everything sharp and actually look better.
timotimo tee hee 12:20
nwc10 so it doesn't surprise me that cameras were recording in 240p
timotimo when i want stuff to be really really sharp, i set my resolution to 16k x 16k and increase the dpi so that everything is rendered bigger too
so i get multisampled antialiasing
just kidding, i haven't actually tried the "increase dpi" part of that 12:21
but it's very funny that i can just use the biggest size that the GPU will offer with a monitor that can't 12:22
MasterDuke ugh, i still can't find a monitor i want (caveat-ed with...and am willing to pay for) 12:25
timotimo by now i don't even see the single pixel vertical line that's broken on my left monitor any more 12:36
MasterDuke timotimo: change of topic. i saw your comment about how slow it was to get a stack trace with tracey. istr its docs saying something about -fno-omit-frame-pointer (which we don't set), do you know if that would make a difference? 12:39
timotimo i set that in my local makefile, or at least i think i did 12:43
yes, i did set that
thing is, i was taking stacks every time a piece of memory from the fsa was allocated or freed 12:44
MasterDuke oh, ha
heaptrack will show you that
timotimo if you have very small frames getting called, that's an alloc and a free extremely close together, and if you have a tight loop or something, it'll be extremely many calls per second
MasterDuke but yes, it slows things down
timotimo does heaptrack track every single allocation's lifetime, too? 12:45
MasterDuke i think so. it has a stat it calls temporary allocations 12:46
timotimo because in tracy you can see for any given address (doesn't have to be an actual memory address, can be any value as long as they aren't re-used and only freed after allocation and such) when (in time) and where (in stacktrace) it was allocated and freed
MasterDuke it might just track it enough to decide whether it considers it temporary or not, i don't think you can see *when* individual alloc/free happen 12:48
timotimo in any case, i love that visualization tracy has for allocations and frees in the "memory map" 12:50
MasterDuke yeah, heaptrack doesn't have that
timotimo and of course scrubbing through the timeline is fun
lizmat and yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2021/05/10/2021-...-beta-pod/ 19:04

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!