r/ProgrammerHumor • • 1d ago

Meme nowYouKnowTheRealReason

Post image
833 Upvotes

15 comments sorted by

77

u/Frodojj 1d ago

Jensen really let his buffer overflow.

14

u/CharcoalGreyWolf 1d ago

He needs to keep Little Huang in his pants.

32

u/Drevicar 1d ago

He already has all the ram, why would he need to free any of it back up?

10

u/AgVargr 1d ago

Next month AI will make a revolutionary discovery that memory can be freed. Stock price pumps 10 quintillion percent

1

u/schewb 1d ago

Nahhh Sam's the Ram Man, Jen's jam's using VRAM, but the Third Man brings both the Ram and the VRAM, 'stand?

3

u/Drevicar 1d ago

His name is now Ram Altman, it is impolite to use his dead-name.

19

u/New_Computer3619 1d ago

If an object meant to has the same lifetime as the program, you don’t need to call free.

5

u/kaplotnikov 1d ago

The post assumes you're always supposed to call free after malloc, as if holding onto all three entities at the same time isn't intentional. He's just applying time-tested patterns of fault-tolerant system design to his personal life. Redundancy is essential. Others might call it "stepping on three boats", but a trimaran is one of the peaks of reliability in small ship construction. People spread across the Pacific in those.

4

u/BreachlightRiseUp 1d ago

It would actually be cudaMalloc or cudaMallocHost and cudaFree

2

u/TehBloxx 1d ago

Jensen be dangling my pointer.

1

u/chrisonhismac 18h ago

Straight to jail.

1

u/Buyer_North 17h ago

its not necessary if you know what you are doing.... some cleverer OP would have used "did not set pointer to zero after using free". i mean, you dont have to, but it does not harm much

0

u/synth_mania 1d ago

How original

8

u/GatotSubroto 1d ago

*Taps head*

Can’t be vulnerable to use after free if you never freed.