V6 beta seems to crash / not respond (so far randomly?)

DL6ER · October 19, 2023, 5:46pm

Sorry, I missed your question. Am I right that silence is a good sign?

"Many" clients could also mean that some of them regularly rotate their MAC addresses for pseudo-anonymity. They appear as new clients in Pi-hole as well - even when Pi-hole is trying to de-pseudo-anonymize them.

bonsi · October 19, 2023, 5:58pm

Sorry about that - but yeah, i started it normally and no crashes so far.

(Running for a couple of days now)

bonsi · October 20, 2023, 12:10pm

Deleted that post because i ran into an issue, which is already fixed and thought it may be because of that built.

DL6ER · October 20, 2023, 6:08pm

github.com/pi-hole/FTL

Fix possible heap overflow

pi-hole:development-v6 ← pi-hole:fix/network_clients_heap

opened 06:00PM - 20 Oct 23 UTC

DL6ER

+6 -6

# What does this implement/fix? Install safety-measured to prevent possible h…eap overflow in the network table processing. This overflow was happening internally because of insufficient memory allocation, it is not possible to trigger this remotely nor to inject anything into the heap. Hence, I am not marking this SECURITY. Discussion around this issue: https://discourse.pi-hole.net/t/v6-beta-seems-to-crash-not-respond-so-far-randomly/65517/23?u=dl6er **Related issue or feature (if applicable):** N/A **Pull request in [docs](https://github.com/pi-hole/docs) with documentation (if applicable):** N/A --- **By submitting this pull request, I confirm the following:** 1. I have read and understood the [contributors guide](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against. 2. I have commented my proposed changes within the code. 3. I am willing to help maintain this change if there are issues with it later. 4. It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1) 5. I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)) ## Checklist: - [x] The code change is tested and works locally. - [x] I based my code and PRs against the repositories `developmental` branch. - [x] I [signed off](https://docs.pi-hole.net/guides/github/how-to-signoff/) all commits. Pi-hole enforces the [DCO](https://docs.pi-hole.net/guides/github/dco/) for all contributions - [x] I [signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) all my commits. Pi-hole requires signatures to verify authorship - [x] I have read the above and my PR is ready for review.