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

Segfaults with 0.4.17 release #180

Closed
robbrit opened this issue Sep 23, 2020 · 4 comments
Closed

Segfaults with 0.4.17 release #180

robbrit opened this issue Sep 23, 2020 · 4 comments

Comments

@robbrit
Copy link

robbrit commented Sep 23, 2020

When using Locust (built on top of gevent) I get a greenlet error message followed by a segmentation fault upon startup:

/usr/local/lib/python3.7/importlib/_bootstrap.py:219: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject
  return f(*args, **kwds)
/usr/local/lib/python3.7/site-packages/locust/util/deprecation.py:17: DeprecationWarning: Usage of User.task_set is deprecated since version 1.0. Set the tasks attribute instead (tasks = [UserBehaviour])
  DeprecationWarning,
[2020-09-23 22:53:24,332] 2887b8bc47e8/INFO/locust.main: Starting web interface at http://0.0.0.0:8089 (accepting connections from all network interfaces)
[2020-09-23 22:53:24,339] 2887b8bc47e8/INFO/locust.main: Starting Locust 1.2.3
Segmentation fault (core dumped)

I believe this to be a greenlet problem because greenlet 0.4.17 was just released yesterday, and rolling back to 0.4.16 fixes the problem:

pip install greenlet==0.4.16
@jamadden
Copy link
Contributor

Please see #178 and install a newer version of gevent or an older greenlet.

@robbrit
Copy link
Author

robbrit commented Sep 23, 2020

Thanks, I bet you guys have been getting spammed all day :)

FWIW using the latest gevent still got the seg fault, only fix was to roll back greenlet.

@jamadden
Copy link
Contributor

Ok, then perhaps locust also has an ABI dependency. I assumed gevent was the only ABI dependency. Thanks for the report! Do you have a github or other link to file an issue with them?

@robbrit
Copy link
Author

robbrit commented Sep 23, 2020

Trying to reproduce on a fresh virtualenv and can't do it. Must have been some sort of version mismatch somewhere, so just ignore me for now.

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

No branches or pull requests

2 participants