will be helpful for those in need Do you have any reason to expect your heap to slowly grow in size? It looks like in both traces it is growing. One thing I've done on many occasions is reduce my heap to try to make the problem worse. However, 256M is about the lower limit for Scala. One thing I've noticed before is that if you have short-lived objects that make it out of the eden generation due to too much pressure it can gradually kill you. This can happen when there's a burst of activity (maybe you have a burst in the morning?) and your eden space isn't big enough. Scala in general and actors in particular make heavy use of small short-lived objects, and it seems there's this magic threshold that once you cross it's all down hill. So one run will be fine and the next crashes and burns.
How do I change actors.maxPoolSize in scala from java?
I think the issue was by ths following , So I have two bash scripts. One for calling the bytecode using the "scala" command, the other to call the same code using the "java" command. My problem is the following, when I use scala, I can see that I can get about 80 threads ( which I created, and shows in my "Task Manager" ) while when I use the java command, I only get about 20 threads created. instead of 80. What is the equivalent "define" option under java for actors.corePoolSize and actors.maxPoolSize? , As far as I know, you can set System Properties in your application: