sman
sman

Reputation: 85

Gatling - GC overhead limit exceeded

I am getting the following error when I tried to Initiate my test. The test includes a large feeder which loops for 620,000 and has a map of 120 items with in the feeder.

Uncaught exception when running trip_dte: java.lang.OutOfMemoryError: GC overhead limit exceeded
[error] sbt.ForkMain$ForkError: java.lang.OutOfMemoryError: GC overhead limit exceeded
[error]     at scala.collection.immutable.HashMap$HashTrieMap.updated0(HashMap.scala:358)
[error]     at scala.collection.immutable.HashMap.$plus(HashMap.scala:62)
[error]     at scala.collection.immutable.HashMap.$plus(HashMap.scala:36)
[error]     at scala.collection.mutable.MapBuilder.$plus$eq(MapBuilder.scala:29)
[error]     at scala.collection.mutable.MapBuilder.$plus$eq(MapBuilder.scala:25)
[error]     at scala.collection.generic.Growable.$anonfun$$plus$plus$eq$1(Growable.scala:59)
[error]     at scala.collection.generic.Growable$$Lambda$44/1950093417.apply(Unknown Source)
[error]     at scala.collection.IndexedSeqOptimized.foreach(IndexedSeqOptimized.scala:32)
[error]     at scala.collection.IndexedSeqOptimized.foreach$(IndexedSeqOptimized.scala:29)
[error]     at scala.collection.mutable.WrappedArray.foreach(WrappedArray.scala:38)
[error]     at scala.collection.generic.Growable.$plus$plus$eq(Growable.scala:59)
[error]     at scala.collection.generic.Growable.$plus$plus$eq$(Growable.scala:50)
[error]     at scala.collection.mutable.MapBuilder.$plus$plus$eq(MapBuilder.scala:25)
[error]     at scala.collection.generic.GenMapFactory.apply(GenMapFactory.scala:48)

Upvotes: 1

Views: 246

Answers (1)

Stéphane LANDELLE
Stéphane LANDELLE

Reputation: 6600

You don't provide enough information to be able to figure out your issue.

Possible issues:

  • you're using an eager feeder (large CSV like feeders are lazy in modern Gatling version, but no idea which Gatling version or which kind of feeder you use).
  • your system under load or your bandwidth can't handle the load you're trying to generate and your virtual users pile up in memory (can't complete their journey and no virtual users keep on arriving).

Upvotes: 1

Related Questions