Inexplicable stuck active thread

Hi, I’m using a quite simple uniformRandomSwitch in a repeat loop and I’m getting ~10% Thread stuck in active during an infinite time.
I don’t know if anyone encountered such a situation and knows how to prevent that.

My code:
val browseContent: ChainBuilder = repeat(5, “n”){
uniformRandomSwitch(
//Ireland
// exec(http(s"A2a-cork_content").get("/ferry-routes/ireland-france-ferries/cork-roscoff/about")).pause(new DurationInt(2).seconds),
// exec(http(s"A2b-bilbao_content").get("/ferry-routes/ireland-spain-ferries/rosslare-bilbao/about")).pause(new DurationInt(2).seconds),
exec(http(s"A2d-sail_content").get("/information/sailing-updates")).pause(new DurationInt(2).seconds),
exec(http(s"A2e-clubvoy_content").get("/information/about-club-voyage")).pause(new DurationInt(2).seconds),
exec(http(s"A2i-contact_content").get("/information/contact")).pause(new DurationInt(2).seconds),
exec(http(s"A2f-genfaq_content").get("/information/faqs")).pause(new DurationInt(2).seconds),
exec(http(s"A2g-petfaq_content").get("/information/faqs/pet-travel")).pause(new DurationInt(2).seconds),
exec(http(s"A2h-disfaq_content").get("/information/faqs/disability-and-reduced-mobility")).pause(new DurationInt(2).seconds)
)
}

Gatling version?

Indeed Stéphane, sorry:
Gatling 3.3.1
runned through scalaVersion := “2.12.10” with sbt

This version was released 1.5 years ago.
You should really consider upgrading.

If it turns out it’s indeed a bug:

  • it might be already fixed in a more recent version
  • otherwise, fix will only happen in 3.6