# \[Filebeat : v7.9.3\] Invalid memory address or nil pointer dereference

**URL:** <https://discuss.elastic.co/t/filebeat-v7-9-3-invalid-memory-address-or-nil-pointer-dereference/313958>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 8, 2022, 7:57am UTC](https://discuss.elastic.co/t/filebeat-v7-9-3-invalid-memory-address-or-nil-pointer-dereference/313958 "2022-09-08T07:57:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![iamyeka](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iamyeka/32/110640_2.png) [@iamyeka](https://discuss.elastic.co/u/iamyeka)\
**Post date:** [September 8, 2022, 7:57am UTC](https://discuss.elastic.co/t/filebeat-v7-9-3-invalid-memory-address-or-nil-pointer-dereference/313958/1 "2022-09-08T07:57:48Z")

</div>

Filebeat version: 7.9.3

I met some issue about "invalid memory address or nil pointer dereference" which caused a panic. But i cannot figure out why that happened. Below is the stack of the panic.

```auto
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x402b74]

goroutine 182 [running]:
github.com/elastic/beats/v7/libbeat/monitoring/report/log.makeDeltaSnapshot(0xc04faaee10, 0xc04faaee40, 0xc04faaee70, 0xc04faaeea0, 0xc04faaeed0, 0xc00702b950, 0xc00702b980, 0xc00702b9b0, 0xc00702b9e0, 0xc00702ba10, ...)
	/go/src/netease.com/libbeat/monitoring/report/log/log.go:174 +0x452
github.com/elastic/beats/v7/libbeat/monitoring/report/log.(*reporter).snapshotLoop(0xc000a9c660)
	/go/src/netease.com/libbeat/monitoring/report/log/log.go:136 +0x2b6
github.com/elastic/beats/v7/libbeat/monitoring/report/log.MakeReporter.func1(0xc000a9c660)
	/go/src/netease.com/libbeat/monitoring/report/log/log.go:107 +0x50
created by github.com/elastic/beats/v7/libbeat/monitoring/report/log.MakeReporter
	/go/src/netease.com/libbeat/monitoring/report/log/log.go:105 +0x15c

```

---

<div class="post-metadata">

**Author:** ![mtojek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mtojek/32/63863_2.png) [@mtojek](https://discuss.elastic.co/u/mtojek)\
**Post date:** [September 8, 2022, 8:23am UTC](https://discuss.elastic.co/t/filebeat-v7-9-3-invalid-memory-address-or-nil-pointer-dereference/313958/2 "2022-09-08T08:23:02Z")

</div>

Hi,

could you check if it's reproducible with a newer version of filebeat?

---

<div class="post-metadata">

**Author:** ![iamyeka](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iamyeka/32/110640_2.png) [@iamyeka](https://discuss.elastic.co/u/iamyeka)\
**Post date:** [September 8, 2022, 8:29am UTC](https://discuss.elastic.co/t/filebeat-v7-9-3-invalid-memory-address-or-nil-pointer-dereference/313958/3 "2022-09-08T08:29:10Z")

</div>

The point is it happens occasionally. Not very often, maybe once a few weeks.  
Because the problem happened in our production environment, i cannot update to a newer version of filebeat immediately.

---

<div class="post-metadata">

**Author:** ![iamyeka](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/iamyeka/32/110640_2.png) [@iamyeka](https://discuss.elastic.co/u/iamyeka)\
**Post date:** [September 8, 2022, 8:30am UTC](https://discuss.elastic.co/t/filebeat-v7-9-3-invalid-memory-address-or-nil-pointer-dereference/313958/4 "2022-09-08T08:30:46Z")

</div>

The key code is here:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/0/108004af2aca9ecaec5511c6ca84fd74a3a9d931.jpeg)

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/0/40bb0bf67e9b30b8cd4e459f26b97ee186ec934e.jpeg)

From the code i don't know under what circumstance the panic could happen

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 6, 2022, 10:31am UTC](https://discuss.elastic.co/t/filebeat-v7-9-3-invalid-memory-address-or-nil-pointer-dereference/313958/5 "2022-10-06T10:31:09Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.