LasterAlex

After some time, pain of windows development and lack of success i gathered that much: 1. It is not a memory leak (it's rust), all the memory actually gets used,...

> Actually, it has nothing to do with `teloxide`, but actually with `tokio` runtime, iirc. > It's possible to create the runtime with increased stack-size for worker-threads (you need to...

@mastermindbaguvix can't recreate on the same rust and teloxide versions, linux is `Linux 6.9.3-76060903-generic` I used `inline` example, does it trigger an overflow for you? If not, could you please...

@Hirrolot This issue is so strange and so inconsistent, but it probably boils down to teloxide using over 1Mb of stack _somewhere_, so I fixed the stack size to 1Mb...

I don't know what this error even means, could you please provide an example of this error? We're mostly tied without one And what did you change? Do you use...

Do you specifically need the currency fix? `0.13.0` should work fine, at least in my testing You also could just increase the stack size using the code snippet i provided...

@hirrolot Well, I kinda? managed to make it on linux ```rust use serde::{Deserialize, Serialize}; use std::error::Error; use dotenv::dotenv; use dptree::deps; use teloxide::{ dispatching::dialogue::{self, serializer::Cbor, ErasedStorage, RedisStorage, Storage}, prelude::*, }; pub...

Storing it in a redis storage That's why `InMemStorage` works fine i assume, there is no serialization

There are 2 problems, both of them are in serde One for incoming `Message` update deserialization (the original issue), and another is... Im not sure if its serialization or deserialization,...

Either optimizing `teloxide` itself (slow and may not yield that much results) Or trying to find a way to spawn a thread with more (or custom) amount of stack for...