archimondain
I would like to know if the function
Process.exit(pid, :kill)
Is synchronous : once the function has returned, are we sure that no more code from the process pid will be executed ? If not how could we kill a process in a synchronous way ?
Best
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app?
Looking for hints regarding:
Addi...
New
Hi all, I wanted to ask how the community is dealing with post-release steps.
Today we have Ecto migrations, which make sure that the db...
New
Kia ora,
We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
Hello,
I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance o...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










First 7 of 7 Posts
lud
I am not sure that the function is synchronous, but to be sure, you could first set a monitor on the process with
Process.monitor, then kill it, then wait for the:DOWNmessage from the monitor.Qqwy
Because the Elixir documentation (as well as the Erlang documentation of
:erlang.exit/2, which this function delegates to) only mention “sends an exit signal”, I am fairly certain that the function is asynchronous.The approach mentioned by @lud works. However, this will not (always) prevent other code from running on
pidbefore it exits. It will only prevent code running on the process callingProcess.exitto wait with continuing beforepidhas exited.However, another question would be: what are you trying to do? It seems like a rather odd request. Maybe your actual problem can be resolved in a wholly different manner.
archimondain
Here is what I try to achieve : I want to run a process and be able to kill it if needed. When the process is either killed or terminates normally, there is a piece of code that I always want to run.
The issue I see with
@lud’s solution is the following : To monitor a process, you need a pid. So when you call themonitorfunction the process is normally already running. It may even be over by the time you call themonitorfunction, in which case you will never receive theDOWNmessage you expect (thisDOWNmessage would trigger the piece of code you always want to execute when a process finishes).Am I making sense ?
Qqwy
From the documentation of Process.monitor/1:
So you will receive the
:DOWNmessage in that case as well.archimondain
Well, then it seems to be a good way to implement what I want
lud
Also if you call
Process.monitoron a pid that is not alive, the down message will contain:noprocas the reason, so you will know your process was not alive.zkessin
if you use spawn_monitor/3 you will remove the race condition on starting the process