[Question] Why does the total value decrease when the "_mi_stats_print" function is executed for each TLD?

Open
#1,208 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c

Research direction

Start at the _mi_stats_print entry point and compare its behavior in mimalloc 2.1.2 and 3.0.8. Reproduce repeated per-TLD statistics printing with the provided mi_custom_thread_stats_print_out wrapper, then determine why the reported total decreases and document the relevant version change.

Written by the indexing model from the issue text.

Description

Hi, thank you for your work on this project.

Image

In our proxy server project, which uses mimalloc as the memory manager, we maintain statistics for each TLD using a dedicated structure when the server process runs. We have implemented an interface function that allows us to print stats for each TLD using _mi_stats_print, as shown below. However, as you can see in the attached screenshot, we have observed that the value of "total" decreases when this is done.

void mi_custom_thread_stats_print_out(mi_stats_t* tid_stat, mi_output_fun* out, void* arg) mi_attr_noexcept {
  _mi_stats_print(tid_stat, out, arg);
}

This issue did not occur with mimalloc version 2.1.2, but started happening after upgrading to version 3.0.8. Do you have any idea what might be causing this?
For reference, the screenshot only shows the output for the “pssv#1” thread, filtered from the _mi_stats_print results using grep.

Dominant language
C
Stars
13.6k
Forks
1.2k
Avg merge
18h 12m
Merged PRs (30d)
20

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/mimalloc

All issues in microsoft/mimalloc

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.