Comments (3)
cheatfate
commented on May 25, 2024
Sorry but this is not Chronos bug, but new bug of Nim compiler. This function do not touch any global values which are in GC memory.
Until @Araq will not explain new gcsafe behavior properly in documentation or specification this issue will be closed.
from nim-chronos.
zah
commented on May 25, 2024
@cheatfate, the issue is that the code makes a call through a function pointer, which is not marked with gcsafe. The function pointer type is this one:
nim-chronos/chronos/asyncloop.nim
Line 243 in 9f15c6b
Since the pointer is not gcsafe, in theory it's possible that a non-gcsafe function is assigned to it, so the compiler has to make the conservative assumption that the caller of the pointer (writeStreamLoop) may not be gcsafe as well.
from nim-chronos.
cheatfate
commented on May 25, 2024
from nim-chronos.
Related Issues (20)
- Implicit returns generates warnings HOT 1
- return statement in try/finally block breaks executing multiple await statements in finally block HOT 1
- Switch AsyncFD to use kEVENT on OSX / *BSD's for Asynchronous thread notification? HOT 3
- compiler error on simple async proc HOT 1
- asyncloop `isCounterLeaked` returns incorrect value?
- chronos is not available in Nim Playground? HOT 2
- httpclient: The content of HostHeader is incorrect when redirecting to a different host HOT 1
- Write to `Future.internalValue` directly in macro-translated code
- `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
- ambiguous identifier: `'Result'` HOT 2
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.