{"version":"2.1.265","anchor":"sharp-removed-from-native-addon-leak-diagnostic-message","canonical_anchor":"sharp-removed-from-native-addon-leak-diagnostic-message","heading":"'sharp' removed from native-addon leak diagnostic message","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/sharp-removed-from-native-addon-leak-diagnostic-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### 'sharp' removed from native-addon leak diagnostic message\n\nThe native-addon memory-leak warning no longer mentions 'sharp' as an example, only node-pty\n\n**What**\n\nWhen Claude Code warns that native memory usage may indicate a leak in a native addon (a compiled module outside plain JavaScript), the message used to list `sharp` and `node-pty` as example addons that might be responsible. It now lists only `node-pty`.\n\n**Why**\n\nThis narrows the example in the diagnostic message; it suggests `sharp` is no longer relevant to this warning, though the finding doesn't say why it was removed.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}