SeleniumHQ / SeleniumHQ/docker-selenium
[🐛 Bug]: java.lang.OutOfMemoryError
Open
Nobody has claimed this yet.
I-OOM
R-awaiting-answer
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 2.5k
- Avg merge
- 10h 16m
- Merged PRs (30d)
- 20
Description
What happened?
Getting oom in eventbus container
Command used to start Selenium Grid with Docker (or Kubernetes)
helm
Relevant log output
{"class": "EventBusCommand","log-level": "INFO","log-message": "Started Selenium EventBus 4.26.0 (revision 69f9e5e): https:\u002f\u002f10.232.86.222:5557","log-name": "org.openqa.selenium.grid.commands.EventBusCommand","log-time-local": "2024-12-14T07:31:37.796Z","log-time-utc": "2024-12-14T07:31:37.796Z","method": "execute"}
Exception in thread "iothread-2" java.lang.OutOfMemoryError: Cannot reserve 8192 bytes of direct buffer memory (allocated: 501211210, limit: 501219328)
at java.base/java.nio.Bits.reserveMemory(Bits.java:178)
at java.base/java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:121)
at java.base/java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:332)
at zmq.io.coder.DecoderBase.<init>(DecoderBase.java:46)
at zmq.io.coder.Decoder.<init>(Decoder.java:71)
at zmq.io.coder.v2.V2Decoder.<init>(V2Decoder.java:18)
at zmq.io.StreamEngine.handshake(StreamEngine.java:805)
at zmq.io.StreamEngine.inEvent(StreamEngine.java:386)
at zmq.io.IOObject.inEvent(IOObject.java:85)
at zmq.poll.Poller.run(Poller.java:275)
at java.base/java.lang.Thread.run(Thread.java:840)
Operating System
k8s
Docker Selenium version (image tag)
4.26.0-20241101
Selenium Grid chart version (chart version)
0.37.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the EventBusCommand entry point and the java.nio and ZeroMQ stack trace in the report, using the 4.26.0-20241101 image and 0.37.1 Helm chart. Reproduce the out-of-memory failure in Kubernetes and determine whether it is caused by the deployment configuration or the event bus. Done means the cause is confirmed and a tested fix or configuration change is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, helm, java, kubernetes
- Domain
- devops, distributed-systems, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100