Why Multi-Threaded Code Can Sometimes Misbehave (Weak Memory Concurrency) - Computerphile @Computerphile
Why Multi-Threaded Code Can Sometimes Misbehave (Weak Memory Concurrency) - Computerphile  @Computerphile
Uploaded May 2026 | Updated November 2026, 2 days ago
Learn more and apply to Jane Street’s WiSE program in New York, London or Hong Kong: jane-st.co/Computerphile-WiSE-2026 (episode sponsor)
Professor Azalea Raad leads the Veritas Lab at Imperial College London... More information about this video in the full description below.

This video is about how Weak Memory Concurrency can cause multiple threads to do unexpected things!

Azalea Raad: profiles.imperial.ac.uk/azalea.raad

Learn more and apply to Jane Street’s WiSE program in New York, London or Hong Kong: jane-st.co/Computerphile-WiSE-2026

Computerphile is supported by Jane Street. Learn more about them (and exciting career opportunities) at: jane-st.co/computerphile

This video was filmed and edited by Sean Riley.

Computerphile is a sister project to Brady Haran's Numberphile. More at bradyharanblog.com
Why Multi-Threaded Code Can Sometimes Misbehave (Weak Memory Concurrency) - ComputerphileCloning Yourself in AI using LoRA  - ComputerphileGarbled Circuits - ComputerphileTETRA Vulnerability (TETRA:BURST) - ComputerphileFinding Hardware Bugs - ComputerphileJensen Huang on GPUs - ComputerphileProcedural Generation in Games - ComputerphileCoffee with Brian Kernighan - ComputerphileHow Bzip2 Works (Burrows Wheeler Transform) - ComputerphileWhat Was Your First Computer Game? (Soundcheck Question 2023) - ComputerphileTCP a : Ensuring Your Data Gets There & in the Right Order! - ComputerphileInside the CPU - Computerphile
Computerphile |

Why Multi-Threaded Code Can Sometimes Misbehave (Weak Memory Concurrency) - Computerphile

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER