LinkedIn uses 2.4 GB RAM across two tabs

LinkedIn’s RAM/CPU Usage and Performance

  • Many report LinkedIn consuming gigabytes of RAM and significant CPU, even on modern machines and phones (fast battery drain, stuttering audio, dropped frames on iOS).
  • Others see lower numbers but still describe it as “heavy” compared to simpler sites.
  • Similar complaints are made about AWS/Azure consoles, Cloudflare dashboard, Stripe, YouTube, BestBuy, and Slack/Electron apps.

Technical Explanations and Browser Issues

  • Suspected causes: memory leaks when scrolling feeds, huge JS/CSS/HTML payloads, heavy frameworks (React/Ember, virtual DOM, immutable state, GC thrash), multiple layered webapps, numerous third‑party scripts, CSS filters, and client-side tracking.
  • Some note browsers aggressively cache and use “discardable” memory, arguing RAM usage is opportunistic; critics reply this still displaces OS caches, triggers OOM killers, and hurts low‑RAM systems and SSDs.
  • Several argue developers and browser teams optimize for their own powerful machines, masking inefficiencies.

Dark Patterns, Tracking, and Anti-Bot Measures

  • Scroll hijacking, artificial drag, and constant notification badges are seen as deliberate engagement hacks that break keyboard nav and accessibility.
  • Anti-scraping / anti-bot iframes and extension detection are mentioned as additional bloat; some welcome blocking spammers, others see it as protecting paid data products.

Value and Use Cases of LinkedIn

  • Despite dislike for the UX, many say it remains the primary job and recruiting platform, especially after alternatives (e.g., Stack Overflow Jobs) disappeared.
  • Uses cited: inbound recruiter leads, sourcing candidates, sales prospecting, investor visibility, maintaining professional contact lists, messaging ex‑colleagues, niche technical and research discussions, and even casual games.
  • Several report multiple good jobs obtained via LinkedIn; others say they never got value and have deleted accounts.

Culture and Social-Media Critique

  • The feed is widely criticized as “cringe” corporate-speak, AI‑generated slop, inspirational/trauma‑to‑business “lessons,” and self‑promotion.
  • Some treat it as a professional “agora” with higher skin-in-the-game; others doubt posts meaningfully affect careers except in extreme cases.
  • Broader dislike of social media business models, personalization feeds, and attention-hoarding is expressed; HN and forums are contrasted as topic‑centric and non‑personalized.

Proposed Coping and Improvements

  • Common advice: use ad/tracker blockers, hide the feed with custom filters, keep a minimal profile, and interact via email or third‑party chat bridges.
  • Suggestions include browser-level RAM limits per tab, better resource reporting, and rewarding performance work inside organizations.