claude-code [BUG] MaxListenersExceededWarning

(node:2760906) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. MaxListeners is 10. Use events.setMaxListeners() to increase limit (Use node --trace-warnings ... to show where the warning was created)

This warning appears at random when using claude on terminal.

Jun 24 '25 01:06 JohnDotOwl

Same here. Happened with the most recent update.

(node:17379) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. MaxListeners is 10. Use events.setMaxListeners() to increase limit        
(Use `node --trace-warnings ...` to show where the warning was created)

Jun 24 '25 02:06 poppabear8883

Getting the same error.

Jun 24 '25 02:06 sbrkopac

Same here

(node:76582) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit

Jun 24 '25 02:06 okhaimie-dev

same

Jun 24 '25 04:06 gbertb

getting the same error too : (node:93282) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. MaxListeners is 10. Use events.setMaxListeners() to increase limit

Jun 24 '25 05:06 teito-dev

Hey, we're looking into this. Can you share when this started? Was it with today's release (1.0.33) or before? Also, what version of node are you running (node -v)?

Jun 24 '25 05:06 ashwin-ant

Hey, we're looking into this. Can you share when this started? Was it with today's release (1.0.33) or before? Also, what version of node are you running (node -v)?

Today, about 4-5hrs ago for me

Jun 24 '25 06:06 okhaimie-dev

got this as well

Jun 24 '25 06:06 yipingbenjaminl

Does this happen at any time or just in plan mode?

Jun 24 '25 06:06 ashwin-ant

anytime, usually after about 30 minutes of usage, it starts happening

Jun 24 '25 06:06 yipingbenjaminl

Hey, we're looking into this. Can you share when this started? Was it with today's release (1.0.33) or before? Also, what version of node are you running (node -v)?

node version is v20.18.1 here. It started with claude 1.0.33 afaiu.

Jun 24 '25 06:06 pmatos

Hey, we're looking into this. Can you share when this started? Was it with today's release (1.0.33) or before? Also, what version of node are you running (node -v)?

1.0.31 31 is ok i think, didnt see this problem yesterday. I started when update started streaming into my terminals i had like quite a few open

my node is v22.14.0

so it's probably 1.0.32 , i started my session at 7am (+8time zone)

Jun 24 '25 07:06 JohnDotOwl

(node:2587029) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit

Got several today. None before today.

Jun 24 '25 08:06 pierre-warnier

Same here.

Jun 24 '25 08:06 kevin-valerio

node v20.19.3 here; saw this first in claude 1.0.33

Jun 24 '25 08:06 keethburu

Same here

Jun 24 '25 09:06 naseef

(node:25217) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit ~$ claude --version 1.0.33 (Claude Code) ~$ node --version v18.19.1

same. started after today's update.

Jun 24 '25 09:06 paraddox

I started seeing this this morning -Now let me check how this component gets its data by looking for the component class or service provider: (node:839800) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. MaxListeners is 10. Use events.setMaxListeners() to increase limit

Jun 24 '25 09:06 salamfall

Same problem after today's update.

Jun 24 '25 09:06 exileum

same here

Jun 24 '25 10:06 norbinsh

same here

Jun 24 '25 11:06 erenkan

Same

Jun 24 '25 11:06 lukebellis

Same here. It might be either a bug in claude code or claude code should properly set the max listeners value

Jun 24 '25 12:06 tcsenpai

Got this after a few minutes on latest update as well

Jun 24 '25 13:06 jacobomadsen

same here too brothers

Jun 24 '25 13:06 aiqbalsyah

Started with today's release

~ % claude --version
1.0.33 (Claude Code)
~ % node --version
v20.18.0

Jun 24 '25 13:06 adstr123

yes, also getting this.

So what's the deal, what is the effect of having this error?

Jun 24 '25 14:06 stavarc

@ashwin-ant , if claude code came with a context engine like augmentcode's , maybe this error could have been solved. Just joking 😂 Any planned context engine for claude code?

What's the rest of you using ? https://github.com/oraios/serena ?

Jun 24 '25 14:06 JohnDotOwl

Same here

(node:39739) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. Use events.setMaxListeners() to increase limit

Jun 24 '25 15:06 CooperBigFoot

Same. Started yesterday. (node:30263) MaxListenersExceededWarning: Possible EventTarget memory leak detected. 11 abort listeners added to [AbortSignal]. MaxListeners is 10. Use events.setMaxListeners() to increase limit

Jun 24 '25 15:06 iteration