Environment info
firebase-tools: 15.3.0
Platform: macOS
Test case
Since firebase-tools version 15.2.0, where pubsub emulator v0.8.25 was introduced, we encounter 100% cpu usage on the Java process on Mac os M1/M2 when we initiate our pubsub queues. The CPU usage never drops, it's like an infinite loop is going on.
We tried with Java 22 and Java 25 and the same problem occurs (on 3 different machines).
We tried to downgrade firebase-tools to 15.1.0 (which bundles with pubsub emulator v0.8.17) and it worked again like before.
On Linux it works perfectly.
So there must be a bug in the latest release of pubsub.
Steps to reproduce
To reproduce you need a Macbook with firebase-tools > 15.1.0, launch the pubsub emulator and create some queues.
Then watch the cpu usage with the mac monitor tool, you should see the Java process taking all the available cpu.
If you are not able to reproduce I can provide more context on how we initiate our queues.
Thanks in advance for your help !
For now we have downgraded firebase-emulators version to 15.1.0.
Expected behavior
We expect pubsub emulator to not cause full cpu usage.
Actual behavior
The pubsub java process is taking all the cpu available.
Environment info
firebase-tools: 15.3.0
Platform: macOS
Test case
Since firebase-tools version 15.2.0, where pubsub emulator v0.8.25 was introduced, we encounter 100% cpu usage on the Java process on Mac os M1/M2 when we initiate our pubsub queues. The CPU usage never drops, it's like an infinite loop is going on.
We tried with Java 22 and Java 25 and the same problem occurs (on 3 different machines).
We tried to downgrade firebase-tools to 15.1.0 (which bundles with pubsub emulator v0.8.17) and it worked again like before.
On Linux it works perfectly.
So there must be a bug in the latest release of pubsub.
Steps to reproduce
To reproduce you need a Macbook with firebase-tools > 15.1.0, launch the pubsub emulator and create some queues.
Then watch the cpu usage with the mac monitor tool, you should see the Java process taking all the available cpu.
If you are not able to reproduce I can provide more context on how we initiate our queues.
Thanks in advance for your help !
For now we have downgraded firebase-emulators version to 15.1.0.
Expected behavior
We expect pubsub emulator to not cause full cpu usage.
Actual behavior
The pubsub java process is taking all the cpu available.