grafana / grafana/pyroscope-java

libasyncProfiler-linux-x64.so dump in /tmp

Open
#250 1 comment 0 reactions 1 assignee Claimed by @korniltsev-grafanista View on GitHub
Dominant language
Java
Stars
126
Forks
48
Avg merge
4d 14h
Merged PRs (30d)
5

Description

Hi,

we use the current 2.1.2 Version to gather the profiles from our Java wildfly application deployments.

We notice many `-pyroscope` directories in the /tmp directory of the applications.
Within these directories are always a `libasyncProfiler-linux-x64-.so` file.

Over a few days these directories quickly consume 15 GB and going.

Example:
```shell
de:/tmp # ls -l
drwx------ 2 4096 Jan 23 01:25 -pyroscope10007989663887495671
drwx------ 2 4096 Jan 21 15:45 -pyroscope10012825659281281608
drwx------ 2 4096 Jan 21 23:00 -pyroscope10014036742711060812
drwx------ 2 4096 Jan 22 04:30 -pyroscope10016341429057459220
drwx------ 2 4096 Jan 23 05:43 -pyroscope10021521715323384330
drwx------ 2 4096 Jan 22 01:01 -pyroscope10026068663342026847
drwx------ 2 4096 Jan 23 01:06 -pyroscope10030053697773365765
drwx------ 2 4096 Jan 21 22:36 -pyroscope1004060422333700746
drwx------ 2 4096 Jan 21 21:14 -pyroscope10044648473989567707
drwx------ 2 4096 Jan 22 21:57 -pyroscope10050690916701502291
drwx------ 2 4096 Jan 21 10:43 -pyroscope10051623230129472605
drwx------ 2 4096 Jan 23 07:44 -pyroscope10053846548520358818
drwx------ 2 4096 Jan 22 13:42 -pyroscope10054852968457409904
drwx------ 2 4096 Jan 23 10:56 -pyroscope10058046168975555431
drwx------ 2 4096 Jan 22 21:30 -pyroscope100589165838902806
drwx------ 2 4096 Jan 22 11:27 -pyroscope10062468989413554577
drwx------ 2 4096 Jan 22 15:36 -pyroscope1006497513880083840
drwx------ 2 4096 Jan 22 00:16 -pyroscope10074157862200598295
drwx------ 2 4096 Jan 21 16:59 -pyroscope10076555267520939339
drwx------ 2 4096 Jan 21 11:27 -pyroscope10078253711349513142
drwx------ 2 4096 Jan 21 20:53 -pyroscope10086459638048789169

de:/tmp # ls -l -pyroscope10007989663887495671
-rw-r--r-- 1 534792 Jan 23 01:25 libasyncProfiler-linux-x64-d73f214b50539537b06070b954cbc95c10a06024.so
```

We set the following options via envs:

```
PYROSCOPE_APPLICATION_NAME=""
PYROSCOPE_SERVER_ADDRESS=http://localhost:4040
PYROSCOPE_PROFILER_ALLOC=512k
PYROSCOPE_PROFILER_LOCK=10ms
PYROSCOPE_EXPORT_COMPRESSION_LEVEL_JFR=BEST_COMPRESSION
PYROSCOPE_ALLOC_LIVE=true
```

Any idea why the filesystem is crushed with these files ?

Thanks in advance !

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.