hellowub

Although there are already some decimal crates also claim to be fixed-point, such as `bigdecimal`, `rust_decimal` and `decimal-rs`, they all bind the scale to each decimal instance, which changes during operations. They're more like floating point.

This crate primitive_fixed_point_decimal provides real fixed-point decimal types.

Glad to hear this.

Thanks. Any advice is welcomed.

I submitted my project here before when I just wrote it out. Now I have realized all features that I can think (e.g. FreeBSD, libdw, expire memblocks active), fixed all known bugs, tested on CentOS, Ubuntu, Debian and FreeBSD, and have no plan any more on it. Then I post it again here for some new advices.

Besides, if you have a production service with very slow memory leak. The leak is so slow that you do not want to fix it. Then you should try `memleax`. It’s convenient and suitable for this case specially.

Thanks.

I did not know GDB well, and wrote this for fun. wazari972 is going to write a tool using GDB and its python interface. Let's expect for it.

Hm.. I do not know Heroku. Is there any problem that I could fix?

Because target progress's each memory allocation/free API invokes a TRAP, the performance influence depends on how often the target program calls memory APIs. For example, it impacts lightly to nginx with HTTP, while heavily with HTTPS, because OpenSSL calls malloc seriously.

Although performance influence is worthy of consideration, since `memleax` is run to attach the target progress only when you certain it is in memory leak, and stopped after real-time memory leak report, so it is not need to attach the target progress for long time.

-- I have added the above to README.md in new version.

Because you can stop memleax as soon as you get enough memory leak report, so the sampling idea will delay the stopping, which make the impact longer.

-- My English is poor, and hope I can make myself understood.

I did not know GDB and its Python interface. I think it may be a better way. Expect for your tool!

A short time before I met a memory leak problem in production environment. The process began memory leak after long-time running. So I need a tool to detect memory leak of a running process. I searched the web but didn't find one. Then I wrote such a tool myself. I wonder if the tool is useful for others. So I share it here, and wait for your advices.