Issue of 100% CPU usage when closing WebSocket connections.

[Maestro-III]

Prerequisites

• I am using the latest version of Locust
• I am reporting a bug, not asking a question

Description

Custom WebSocket stress test script, environment: 20 cores, 32GB RAM, 1000M bandwidth. Run the script in this environment. Only log in one user and do not send messages, just need to stay online. When clicking STOP on the web UI interface, after 20-30 seconds, a warning appears: 'CPU usage above 90%!'. If using --headless, this problem obviously doesn't occur. However, consider a situation where, during automated loading, this might be unfriendly.

Command line

locust -f mylocustfile.py

Locustfile contents

#!/usr/bin/env python
# -*- coding: utf-8 -*-



class WebSocketUser(HttpUser):
    wait_time = between(1, 2) 

    def on_message(self, ws, message):

    @staticmethod
    def on_close(ws, close_status_code, close_msg):
    
    @staticmethod
    def on_open(ws):
         

    @task
    def pft(self):
        ws = websocket.WebSocketApp('wss:xxxxxxxxxxxxxxxxx&transport=websocket',
                                    on_message=self.on_message,
                                    on_error=self.on_error,
                                    on_close=self.on_close)
        ws.on_open = self.on_open
        self.run_forever_with_retry(ws)
        self.active_websockets.append(ws)

Python version

3.9.12

Locust version

2.20.0

Operating system

Linux \ mac