Comments (5)
I need to understand when EAGAIN
happens, at the end or in process?
from nim-chronos.
in process, the err
var here contains it:
And then it gets raised by the getMessage
call in the handler. The segfault happens only later on a second getMessage
.
from nim-chronos.
But why you are trying to perform one more getMessage()
?
from nim-chronos.
I don't. It gets called automatically by the handler on next data received by same DatagramTransport.
from nim-chronos.
I think I found the root cause of my EAGAIN
error. It is due to a poll() in an async proc (which is not nice anyhow, but that was not the point).
If you look at the poll()
code it makes sense that this can happen, although it requires some conditions.
A "normal" poll()
which adds the async proc with the poll()
inside to the callbacks
and next also the readDatagramLoop
handler on an Event.Read
. processCallbacks
must run first the async proc with poll()
. Next in that poll again Event.Read
for same socket, processCallbacks
runs again, both callbacks are run ... et voila, EAGAIN
So I guess this can be closed, but perhaps some documentation could be added that this should not be done.
from nim-chronos.
Related Issues (20)
- `getAcceptInfo` can raise an unlisted exception: ref ValueError HOT 2
- Apparent garbage collect of localCopy in datagram sendTo before data gets send in writeDatagramLoop HOT 2
- Cycle-based memory Leak under --mm:arc HOT 1
- chronos/threadsync errors when compiling documentation
- bug: TokenBucket update calculates wrong with lastUpdate timestamp HOT 1
- Reading a file asynchronously? HOT 1
- Async proc: both Option[seq[T]] and Opt[seq[T]] as return type and one of the params is generic, failed to compile with Nim-devel HOT 1
- Completing `Futures` in refc may have unexpected behavior HOT 1
- `cancelAndWait` on `or` triggers deadlock
- `SIGSEGV` in `asyncTest`-derived scenario (also, in `asyncTest`) HOT 5
- Can't compile on GCC 14 HOT 1
- ambiguous identifier: `'Result'` HOT 2
- Change header size limits HOT 2
- Its impossible to specify Future[T].Raising([]) as argument.
- What is the intended method for catching exceptions raised from asyncCheck'd Futures? HOT 4
- Why does this usage of asyncSpawn and ThreadSignalPtr leak memory? HOT 4
- Compilation errors with `-d:chronosHandleException` HOT 1
- Hash-order independent tests HOT 5
- Compilation error `invalid pragma: stackTrace: off` HOT 1
- bug: epoch calculation is incorrect HOT 4
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 nim-chronos.