Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segmentation fault running the locust command #2447

Closed
2 tasks done
Rdbaker opened this issue Nov 6, 2023 · 2 comments
Closed
2 tasks done

Segmentation fault running the locust command #2447

Rdbaker opened this issue Nov 6, 2023 · 2 comments
Labels

Comments

@Rdbaker
Copy link

Rdbaker commented Nov 6, 2023

Prerequisites

Description

I followed the Quickstart from the documentation website, and got a segmentation fault on startup:

(tc) √:backend rdbaker $ locust
[2023-11-06 08:50:35,348] Ryans-Macbook-Pro.local/INFO/locust.main: Starting web interface at http://0.0.0.0:8089 (accepting connections from all network interfaces)
[2023-11-06 08:50:35,360] Ryans-Macbook-Pro.local/INFO/locust.main: Starting Locust 2.18.1
zsh: segmentation fault  locust

I'm using a freshly installed Python 3.11.6 and running inside a virtual environment on a mac x86 architecture. I'm more than happy to attach the crash dump if that would be helpful, but it's very verbose, so I decided not to. I also tried running in headless mode to see if it had to do with the server, and that also seg faulted

Command line

locust

Locustfile contents

from locust import HttpUser, task

class HelloWorldUser(HttpUser):
    @task
    def hello_world(self):
        self.client.get("/api/admin/users/1")

Python version

3.11.6

Locust version

2.18.1

Operating system

macOS Big Sur 11.6.6

@Rdbaker Rdbaker added the bug label Nov 6, 2023
@Rdbaker
Copy link
Author

Rdbaker commented Nov 6, 2023

Just tried this on my work laptop instead of personal and it works fine, here are the differences

Python version

3.11.0

Operating system

macOS Monterey 12.5

Chip: Apple M1 Pro

Due to this, I'm assuming this cannot be a locust issue- apologies for the false alarm on the issue here, closing this.

@Rdbaker Rdbaker closed this as completed Nov 6, 2023
@cyberw
Copy link
Collaborator

cyberw commented Nov 6, 2023

I'm glad you got it sorted out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants