You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you used the debugging guide to try to resolve the issue?
Have you checked our FAQs to make sure your question isn't answered there?
Have you checked to make sure your issue does not already exist?
Have you checked you are on the latest release of Pulsar?
What happened?
When starting pulsar, about 20% of the time, it pegs the CPU and the window does not open. The workaround is to kill it and start again.
This behavior is new with version 1.114.0. It did not occur with 1.108.0. (I was not able to use anything between those two versions due to issue #733.)
There are two processes running while the CPU pegged. I did an strace on both of them. One doing this repeatedly:
Just wanted to say thanks for reporting the issue and we will be sure to look at this one, but unfortunately there's been a lot of change between these versions, and with the issue seemingly being random or depending on something local to your system it may be hard to pinpoint.
Since having originally reported this I've had a chance to use the same version of pulsar on several other AlmaLinux 9 hosts. The issue has not shown itself on any of the others.
The thing that makes the original host different is that it is a virtual machine, whereas all of the other hosts are bare metal. The VM software is VirtualBox 7.0.14 running on Windows 10.
Thanks in advance for your bug report!
What happened?
When starting pulsar, about 20% of the time, it pegs the CPU and the window does not open. The workaround is to kill it and start again.
This behavior is new with version 1.114.0. It did not occur with 1.108.0. (I was not able to use anything between those two versions due to issue #733.)
There are two processes running while the CPU pegged. I did an
strace
on both of them. One doing this repeatedly:The other is doing this:
Pulsar version
1.114.0
Which OS does this happen on?
🐧 Red Hat based (Fedora, Alma, RockyLinux, CentOS Stream, etc.)
OS details
AlmaLinux 9
Which CPU architecture are you running this on?
x86_64/AMD64
What steps are needed to reproduce this?
Start Pulsar. If it pegs the CPU and the window does not open, the issue has been reproduced. If the window opens then it is fine.
Additional Information:
No response
The text was updated successfully, but these errors were encountered: