Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate why memory tracker misses ServerFamily::replica_ deallocation #4437

Open
kostasrim opened this issue Jan 10, 2025 · 0 comments
Open
Labels
bug Something isn't working

Comments

@kostasrim
Copy link
Contributor

To reproduce:

  1. Run python3 -m pytest dragonfly/replication_test.py --df allocation_tracker=256:88285184 -k "test_big_containers"
  2. cat log | python3 parse_allocator_tracking_logs.py

Now observe:

Deallocating non existing address: 0x2be840b0000 640
Address: 0x2be840d0e00, Size: 768 bytes, original line: `I20250110 12:09:54.542371 94710 allocation_tracker.cc:79] Allocating 768 bytes (0x2be840d0e00). Stack: 0x59364644d018  std::__allocate_guarded<>()
`
Address: 0x2be843a0b00, Size: 256 bytes, original line: `I20250110 12:09:54.583632 94710 allocation_tracker.cc:79] Allocating 256 bytes (0x2be843a0b00). Stack: 0x5936468cfe88  dfly::ProtocolClient::ProtocolClient()
`
@kostasrim kostasrim added the bug Something isn't working label Jan 10, 2025
@kostasrim kostasrim changed the title Investigate why memory tracker missing ServerFamily::replica_ deallocation Investigate why memory tracker misses ServerFamily::replica_ deallocation Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant