Comments (6)
Proposed fix: change
('dead (error "epoll instance is dead"))))
to
;; This can happen if a fiber was waiting on a condition and run-fibers completes before
;; the fiber completes and afterwards the condition is signalled. In that case, we don't
;; have to resurrect the fiber or something, we can just do nothing.
;; (Bug report: https://github.com/wingo/fibers/issues/61)
('dead #t)))
and add the test to the test suite?
(Edit: clarification: I did not test this.)
from fibers.
Minimal test case:
(use-modules (fibers) (fibers conditions) (fibers scheduler))
(define c (make-condition))
(run-fibers
(lambda ()
(spawn-fiber (lambda () (wait c)))
(yield-current-task)) ; let the other fiber wait forever
#:hz 0 #:parallelism 1) ; it fails both with and without, preemption is another complication, so keep things simple for now by not preempting
(signal-condition! c)
from fibers.
Description:
When a fiber is waiting on a condition and run-fibers completes before the fiber completes and afterwards the condition is signalled, ‘epoll instance is dead’ results.
from fibers.
Sounds like a good fix to me!
from fibers.
Sounds good to me too. @emixa-d can you provide a PR for this? i'll merge right away. thanks!
from fibers.
I've made a PR at: #62
from fibers.
Related Issues (20)
- Something like promises HOT 5
- Test failures with "wrong state" on aarch64 HOT 1
- Expensive tests should be skipped by default
- Failing to create a non-blocking socket inside fiber HOT 2
- Configure dosnt't look up for libgc headers
- Q: Does it support racket? or how to use it in racket HOT 1
- Unbound variable: SOCK_NONBLOCK on MacOS 14.5
- `race-until` test runs forever (1.2.0 + affinity patch, NetBSD 9 amd64) HOT 1
- Cannot print backtraces within a fiber HOT 13
- [doc] clarify the use of dynamic-wind, probably in the Barriers chapter HOT 1
- Guile deprecation warning due to bit-count HOT 9
- Fibers wait can forever on a file descriptor once it has been closed HOT 1
- 'get-message' continuation fired more than once? HOT 13
- On GNU/Hurd, 'time_units_per_microsec' is zero HOT 1
- High CPU usage on system time change HOT 7
- Documentation refers to `send-operation` instead of `put-operation`
- Implementing thread-operation HOT 10
- concurrent-web-server doesn't wait for the server to be started HOT 1
- Missing basic combinators `guard-operation` and `nack-guard-operation`
- fibers does not support wait-operation being interrupted, even when on a non-fibers thread HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fibers.