HelloZeroNet/ZeroNet

ZeroNet freezes during startup because of bogus timeout values passed to kevent.

Open

#1202 opened on Dec 9, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (18,200 stars) (2,245 forks)batch import
bughelp wanted

Description

  • ZeroNet version: 0.6.0
    • Operating system:FreeBSD 11.1
    • Web browser:Chrome
    • Tor status: always
    • Opened port: no
    • Special configuration: n/a

ZeroNet freezes during startup. The problem was traced to the kevent call made by libev from gevent. Bogus timeout value is passed to kevent. gevent maintainer claims that race condition in ZeroNet causes the problem.

See details here: https://github.com/gevent/gevent/issues/1051#issuecomment-350490266

Contributor guide

Tech stack
python
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
understanding of gevent and libevdebugging race conditions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Investigate the race condition described in the linked gevent issue (https://github.com/gevent/gevent/issues/1051#issuecomment 350490266). The problem occurs during startup when bogus timeout values are passed to kevent by libev/gevent. Start by examining the initialization sequence in the ZeroNet codebase where gevent is used, focusing on any timeout handling or socket operations that could lead to invalid state. Consider reproducing the issue on FreeBSD 11.1 to confirm the behavior.