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

27.1 crash (core dump) while running tprof #8835

Open
mkuratczyk opened this issue Sep 20, 2024 · 2 comments · Fixed by #8897
Open

27.1 crash (core dump) while running tprof #8835

mkuratczyk opened this issue Sep 20, 2024 · 2 comments · Fixed by #8897
Assignees
Labels
bug Issue is reported as a bug team:VM Assigned to OTP team VM
Milestone

Comments

@mkuratczyk
Copy link
Contributor

Describe the bug
I wanted to use tprof on a running RabbitMQ node and the Beam crashed completely. I submitted a bunch of commands to the shell at once so I'm not sure which command was executing when it happened.

It looked like this:

> tprof:start(#{type => call_memory}), tprof:set_pattern('_', '_' , '_'), tprof:enable_trace(whereis(ra_log_wal)), timer:sleep(5000), Sample = tprof:collect().
[os_mon] cpu supervisor port (cpu_sup): Erlang has closed
[os_mon] memory supervisor port (memsup): Erlang has closed
make: *** [/home/kura/rabbitmq/server/ra-log-single-memtbl/deps/rabbit_common/mk/rabbitmq-run.mk:275: run-broker] Floating point exception (core dumped)

I've uploaded beam.smp and the core dump here:
https://drive.google.com/drive/folders/1VqXjDjNcvl06moBy4qbL7of1Ym4EEzQ9?usp=drive_link

Affected versions
27.1

@mkuratczyk mkuratczyk added the bug Issue is reported as a bug label Sep 20, 2024
@IngelaAndin IngelaAndin added the team:VM Assigned to OTP team VM label Sep 20, 2024
sverker added a commit to sverker/otp that referenced this issue Oct 3, 2024
into 'sverker/26/erts/trace-bp-hash-reset-bug/erlangGH-8835/OTP-19269'
sverker added a commit to sverker/otp that referenced this issue Oct 3, 2024
into sverker/27/erts/trace-bp-hash-reset-bug/erlangGH-8835/OTP-19269
@sverker
Copy link
Contributor

sverker commented Oct 3, 2024

Thanks for the good report.
This was an over ten-year-old bug.
Proposed fix in #8897.

@sverker sverker linked a pull request Oct 3, 2024 that will close this issue
IngelaAndin pushed a commit that referenced this issue Oct 9, 2024
…69' into maint-26

* sverker/26/erts/trace-bp-hash-reset-bug/GH-8835/OTP-19269:
  erts: Fix bug when resetting call_time/memory while tracing
@sverker sverker added this to the OTP-26.2.5.4 milestone Oct 9, 2024
@sverker
Copy link
Contributor

sverker commented Oct 9, 2024

Fix in OTP-26.2.5.4.

Mikaka27 pushed a commit that referenced this issue Oct 14, 2024
…69' into maint-25

* sverker/25/erts/trace-bp-hash-reset-bug/GH-8835/OTP-19269:
  erts: Fix bug when resetting call_time/memory while tracing
jhogberg pushed a commit that referenced this issue Oct 17, 2024
…69' into maint-27

* sverker/27/erts/trace-bp-hash-reset-bug/GH-8835/OTP-19269:
  erts: Fix bug when resetting call_time/memory while tracing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue is reported as a bug team:VM Assigned to OTP team VM
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants