Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Possible TargetCustom Leak

See original GitHub issue


I am using VIPS on a ASP.NET Core application, in order to avoid frequent allocation of memory, I am using TargetCustom to directly write the output to a PipeWriter that is attached to the HTTP response stream. This works fine on all normal circumstance. However, when the requests to the app increases and the client starts to disconnect abruptly, there seem to be some issue while disposing TargetCustom.

NetVips: 1.2.4
NetVips.Native: v8.10

Here is the error message I am getting: Process terminated. A callback was made on a garbage collected delegate of type 'NetVips!NetVips.Internal.VipsSourceCustom+ReadSignal::Invoke'.

This is rough idea of how my code looks:

            PipeWriter writer; // piped to the HTTP response stream
            using var target = new TargetCustom();
            target.OnWrite += (buffer, length) =>
                var span = new ReadOnlySpan<byte>(buffer, 0, length);
                return length;
            target.OnFinish += () => writer.Complete();

I tried to manually detach the OnWrite and OnFinish delegate, and the error still remains. Is there any work around for this?

Secondly, the same application also seem to have some other issue, occasionally it crashes with: Segmentation fault (core dumped)

on a windows server it produces: The program has exited with code -1073741819 (0xc0000005) 'Access violation'.

Unfortunately I cannot find any other stack trace. Since it is a web app, each request can independently resize images in parallel, I am afraid this may be related to multithreading. The method ConcurrencySet is not used, leaving VIPS to automatically choose based on the number of CPUs. The issue also seems to happen when the main memory is overwhelmed, and is not easily reproduced.

When the app is first initialized, I am statically setting these:


Thank you so much for taking the time to look into the issues.


Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:11 (6 by maintainers)

github_iconTop GitHub Comments

kleisaukecommented, Oct 11, 2020

Sorry for the delay, I should spend more time on replying to issues.

Great to hear that the crashes have been resolved now! I’ve no experience with Kubernetes, but can provide some performance/security tips for image processing with libvips. These tips are mainly based on my experience with, which currently processes 7 million (7×106) images per hour.

  • Avoid using ThumbnailImage, if possible. It can’t do any of the shrink-on-load tricks, so it’s much, much slower.
  • Consider using a different memory allocator such as jemalloc to prevent memory fragmentation in long-running, multi-threaded, glibc-based Linux processes. See to learn more about memory allocation and why the choice of a memory allocator is important.
  • The libvips’ operation cache is not useful for image proxies (i.e. processing many different images). Consider to disable this.
  • Only enable the loading libraries you really need. For example, libvips could open microscope images, which most websites won’t need.
  • Always sanity check image dimensions to protect you from decompression bombs like those described at
jerome-zenfoliocommented, Mar 30, 2021

Thank you Kleisauke & congrats on the 2.0 release!

Read more comments on GitHub >

github_iconTop Results From Across the Web

CMake target compile option leaking to other targets
For this reason info like this should have a visibility that is "as PRIVATE as possible". Note that the project may not be...
Read more >
Defining custom data leak & attack signatures
Attack log messages contain Custom Data Leakage Violation: <rule_name> or Custom ... From Available Target, select which locations in the HTTP request (e.g. ......
Read more >
Target leaked the next event name : r/ApexUncovered
r/ApexUncovered - Target leaked the next event name ... themoonroseup Custom Flair • 2 yr. ago ... The leak came from target, a...
Read more >
Configuring the memory leak policy
Note: You can configure WebSphere Application Server to detect, prevent, and take action, if possible, on classloader memory leaks using the memory leak...
Read more >
Configure VRF Route Leak on Nexus Switches
Limitations. You must leak a route directly from the source VRF into the target VRF. You cannot leak a route that is currently...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found