Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
Get HideMyAss! VPN, PC Mag's Top 10 VPNs of 2016 for 55% off for a Limited Time ×

Comment Re:The Entitled generation (Score 1) 1080

Milennials don't support Socialism. They support being given everything they want without having to work for it and expecting someone else to pay for it.

If you ask a Milennial "How will we pay for giving everyone free homes, cars, food, education, power, water, heat, lights, gasoline/electricity charging, massages or whatever else they decide they want today" the answer will either be "increase taxes on "the rich" (let someone else pay for it)" or "I don't know/that's a good question.".

This. Definitely this.

If you ask them what they want, it's to be given free stuff. (Free for them - obviously someone has to work to supply it, just not them).

They have associated socialism with handouts. Free healthcare. Free education. Free housing. Free entertainment... the list goes on and on.

Sigh.

Comment Only part of the problem. (Score 2) 165

There are two real issues here.

The first is that malicious programs could open up, grab screen buffers, and get access to stuff that had been on the screen to use for their nefarious purposes.

This is bad, and unless we get decent support to isolate the frame buffers (and other graphic memory) between apps at either the driver or hardware layer, it's not going away anytime soon. Dont want this? Power cycle (all the way off - not just hiberante) between application launches would do it.

The second is sloppy programming on the part of non-malicious applications. That's what is being talked about in the application. Diablo apparently asked for a frame buffer, and then presented it, as is, to the user without putting what it wanted in place, trusting for it to be in a particular state. Which it wasn't.

You want a black screen to show to the user, then write zeros into your buffer before you show it to the user. Decent compilers/languages will tell you if you've tried to read from unitialized variables, and you should never trust that anything you've asked for dynamically is in a safe state, unless you've explicitly requested that it's cleared before being handed to you. Why should a resource from the graphics card be treated any differently?

NVidia is right about one thing here - most of the time, nearly all of the time, the thing you do with that buffer you're given is to write your stuff into it, completely overwriting it, and it would slow things down if they had to guarantee that it was cleared before handing it out to you. If your program doesn't care enough to do so itself, that's not really their fault.

It would be nice if, on program exit, all GPU resources used by that app were flushed, but again, that would involve the OS needing to be told of all the GPU resource allocations and deallocations so it could clean up properly, and that too would probably slow things down. Not a lot, but enough to be annoying when your game stutters.

Slashdot Top Deals

1 Sagan = Billions & Billions

Working...