<d1b2>
<johnsel> If the peak is position such that the label will be just on th edge/partially outside the window it gets blurry presumably because it keeps changing position a (few) pixel(s)
<azonenberg>
So, when a peak disappears completely
<azonenberg>
the marker is supposed to fade out over several frames, but if the peak returns it'll come back
<azonenberg>
this is probably an edge case where every frame or two it is/isnt on screen
<azonenberg>
maybe it's showing up as two separate peaks
<azonenberg>
By all means poke at it, but it's low priority in comparison to some of the other stuff i'm working on right now
<d1b2>
<johnsel> That could be it, I can't replicate it now
<d1b2>
<johnsel> I did have a second crash while zooming through the FFT window horizontally and vertically
<d1b2>
<johnsel> I can scroll and middle click let's say 10-15 times but at some point it crashes. Will try to pull some debug info next time
Degi has quit [Ping timeout: 255 seconds]
Degi has joined #scopehal
josuah has quit [Remote host closed the connection]
<_whitenotifier-f>
[scopehal] azonenberg ba386c8 - Window functions now support offsets allowing multiple invocations within a single buffer. Spectrogram now uses GPU based windowing
<_whitenotifier-f>
[scopehal] azonenberg dd39d0f - Removed false graphwidget dependency from apple silicon scopehal build
<d1b2>
<johnsel> I reinstalled the binary install too
<d1b2>
<johnsel> Cursed PC syndrome again I think
<d1b2>
<johnsel> I bought a new motherboard that should be good, I think the CPU + RAM + PSU are next
<d1b2>
<johnsel> I really can't deal with these weird random issues anymore
<d1b2>
<johnsel> I may have a borked Windows install again. It keeps BSODing too every once in 2 weeks or so while idling
<azonenberg>
did you try an older binary build in case it was a regression? ... oh
<azonenberg>
lol
<azonenberg>
in that case i cant help you :p
<d1b2>
<johnsel> it won't even write a dump to the disk that's how bad it BSODs
<d1b2>
<johnsel> I really think it must be the CPU itself at this point
<d1b2>
<johnsel> Yeah I'd try that, if it wasn't for the same version worked last night
<d1b2>
<johnsel> I literally ran the same install and now it crashes with an access violation error
<azonenberg>
yeah your hardware / OS sounds well and truly screwed lol
<azonenberg>
random memory corruption or something
<d1b2>
<johnsel> yeah you'd think memory, it feels like memory. But I have ran hours and hours of memtest, and it clears just fine
<azonenberg>
reminds me of the time i was asked to help a classmate as an undergrad with a compsci 1 homework assignment that was failing to compile under visual studio
<d1b2>
<johnsel> I've removed DDR sticks
<azonenberg>
turns out one of the libc header files had a bitflip in it
<d1b2>
<johnsel> run the system on 1 stick
<d1b2>
<johnsel> no differnce
<azonenberg>
and was giving syntax errors lol
<juh>
i wish the fact that i do server maintenance could help here, but at work we would just casually "swap the cpu" and then "swap the motherboard again" if it didn't work
<azonenberg>
lol
<azonenberg>
yeah if you have a whole datacenter worth of spare parts and just need the thing running again thats the way to do it
<d1b2>
<johnsel> well I started my professional career doing sysadmin, I know how diagnose these issues properly I just don't have/didn't have the budget to buy another set of everything. An
<juh>
the amount of money just floating around on shelves in there is mind boggling
<d1b2>
<johnsel> well yeah, downtime is even more expensive
<d1b2>
<johnsel> I think by law I can order online and have a period of 30 days where I can return without giving the seller a reason for it
<d1b2>
<johnsel> So I will probably just do that with a big vendor that can take the costs of restocking it
<d1b2>
<johnsel> Just buy everything (except the mobo which I alread bought) and swap it out piece by piece until I figure out what is borked