leonardorame
Hi, I built a NIF out of a well known C++ Dicom library called DCMTK. The purpouse of this NIF is to stay loaded for the whole life of my Elixir/Phoenix application, where it’s functions are called many times.
The module that loads this NIF is called from an Agent and I thought it stay there forever, but as it is segfaulting after using it for a while I’m starting to think it is removed from memory after some time…
Let me show my code:
defmodule Prueba3.ImageCache do
use Agent
def start_link(_opts) do
Dcmtknif.initialize()
Agent.start_link(fn -> %{} end, name: :imagecache)
end
def get(key) do
Agent.get(:imagecache, &Map.get(&1, key))
end
def put(key, value) do
Agent.update(:imagecache, &Map.put(&1, key, value))
end
end
defmodule Dcmtknif do
@on_load :load_nifs
def load_nifs do
:erlang.load_nif('./ssr/libssr', 0)
end
def _loadDicomFile(_dicomfile) do
raise "NIF _loadDicomFile/1 not implemented"
end
def _getTagValue(_dcmff, _group, _element) do
raise "NIF getTagValue/1 not implemented"
end
def _getHeader(_dcmff) do
raise "NIF getHeader/1 not implemented"
end
def _getPNG(_dcmff) do
raise "NIF getPNG/1 not implemented"
end
def _setMinMaxWindow(_dcmff) do
raise "NIF setMinMaxWindow/1 not implemented"
end
def _createScaledImage(_dcmff, _width, _height, _interpolate, _aspect) do
raise "NIF createScaledImage/5 not implemented"
end;
def _initialize() do
IO.puts("Dcmtknif.initialize()")
raise "NIF initialize/0 not implemented"
end
def _finalize() do
raise "NIF finalize/0 not implemented"
end
... more functions
end
Do you see something wrong?
Trending in Questions
Hey guys,
I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly
Do you guys have any suggestions what is the best prac...
New
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
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
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
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
whatyouhide
I’m not an expert in NIFs, but in general the VM yields execution to the NIF when you call it, so you’re really not supposed to have “long-running NIFs”. When you enter a NIF, the VM cannot do GC, context, switching, and so on anymore.
I think a common solution in a case like yours, where you have essentially an external program that needs to run continuously, is to use ports. You spawn the program you want to run and you let your Elixir application manage its lifetime. Then, you communicate with the spawned program through stdout.
Does that make sense?
leonardorame
Hi @whatyouhide, I think I wrongly explained what this NIF does. With “long-running” I mean it has state (internal variables pointing to data structures that can be accessed from the parent Elixir process), please don’t confuse with long loops or heavy processes inside it.
Regarding your ports suggestion, I can do that, but it adds complexity on the C++ side and I’m trying to maintain that part as small as possible.
leonardorame
This is where the program crashes, I call the image function ~100 times (not always the same number of times) then it crashes:
jhogberg
I can assure you that the NIF hasn’t been unloaded. You would need to do that manually, and even then the VM takes great care not to pull the rug while anything references it.
I think I can see why it crashes though. What’s preventing
image/2from being called concurrently?leonardorame
Hi @jhogberg, nothing prevents that (in fact, it will be called concurrently at production), but as far as I understand the function
createScaledImage_nifis thread safe (it receives the data that should use to work with by param, no global variables).I added debug messages (
std::cout) everywhere in thecreateScaledImage_nif, and found the app crashes just before entering into that function.jhogberg
Imagine that you get several concurrent calls to
image/2with the samesopinstanceuid.Isn’t there then a pretty good chance that they all end up calling
createScaledImage_nif,setMinMaxWindow_nif, andgetPNG_nifwith the same resource?Also, would you care to share the code for
getPNG_nif?leonardorame
Yes, the program should allow concurrently call
createScaledImage_nif, it has a pointer to a resource with the original image, then this function returns a scaled version of it, never overwriting the original.Here’s the
getPNG_niffunction:leonardorame
I commented the block that uses the cached image (lines 27 to 38) and the program didn’t segfaults. It looks like something is filling the
cachedDcmFFvariable with garbage:jhogberg
You are overwriting
ff_res->_dicomimagehowever, so you’ll at the very least be leaking memory.Please share what happens to
ff_res->_dicomimageinsidewritePNGtoMemory, is there adelete ff_res->_dicomimageor similar in there?Concurrent accesses would do that.
leonardorame
Maybe this is the culpit:
Elixir:
C++