bug-bounty505
xss268
rce153
google149
bragging-post117
facebook112
microsoft112
account-takeover111
exploit91
malware88
csrf86
privilege-escalation85
open-source81
cve80
authentication-bypass80
stored-xss75
reflected-xss63
apple63
web-security63
ai-agents63
access-control63
phishing58
input-validation53
sql-injection49
cross-site-scripting49
defi48
smart-contract48
ssrf46
ethereum45
reverse-engineering45
api-security44
writeup43
information-disclosure43
tool40
dos40
web-application38
privacy38
vulnerability-disclosure37
cloudflare37
web337
browser37
burp-suite37
automation35
lfi34
opinion34
llm34
html-injection33
responsible-disclosure33
supply-chain33
race-condition33
0
6/10
research
A critical analysis of Erlang's actor model and message-passing concurrency, arguing that despite superior isolation through separate process heaps, Erlang still exhibits the four failure modes of shared mutable state (deadlock, unbounded queue growth, message ordering races, protocol violations) through its mailbox design, with all mitigations requiring programmer discipline rather than language enforcement.
concurrency
erlang
actor-model
message-passing
deadlock
shared-mutable-state
system-design
type-safety
backpressure
fault-tolerance
Erlang
Carl Hewitt
Joe Armstrong
Ericsson
Akka
Swift
Orleans
Dapr
Go
WhatsApp
Fred Hébert
pobox
OTP
Fowler and Hu
OOPSLA 2026