Skip to content

Go routine memory allocation issue #181

Closed
@rlagyu0

Description

@rlagyu0

error emit like below

ts=2025-02-25T07:55:33.803Z caller=collector.go:511 level=debug msg="Calling function ScrapeGenericValues()"
ts=2025-02-25T07:55:33.803Z caller=collector.go:616 level=debug msg="Calling function GeneratePrometheusMetrics()"
double free or corruption (out)
SIGABRT: abort
PC=0x7f756d1235ef m=0 sigcode=18446744073709551610
signal arrived during cgo execution

Typically, it fetches data successfully for the first 2-3 times, but it seems that during the memory allocation/deallocation process of goroutines, they get tangled, leading to issues with duplicate memory allocation or deallocation. Please provide your opinion.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions