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

profile! call blocks and leaks memory #115

Open
kpricorn opened this issue Sep 21, 2014 · 1 comment
Open

profile! call blocks and leaks memory #115

kpricorn opened this issue Sep 21, 2014 · 1 comment

Comments

@kpricorn
Copy link

Hi,

I'm using rmagick on OSX to edit jpeg images. Recently I encountered an issues with the profile! (1) method on an image object. The method blocks and memory usage of the ruby process jumps immediately to ~4GB. (see [2]) and I need to kill the process to avoid the system to freeze completely. I'm calling profile! as described in the documentation to remove all profiles from the image.

# Use profile('*', nil) to remove all profiles from the image.
# see attached image
ruby -rrmagick -e 'Magick::Image.read("sample.jpeg").first.profile!("*", nil)'

I tested this with the following versions:

  • OSX 10.9.4
  • rmagick (master, 2.13.3, 2.13.3.rc1, 2.13.2)
  • imagemagick: 6.8.9-7 (installed with homebrew)
  • ruby 2.1.2p95

Did anyone else experience this behaviour? I tried to reinstall imagemagick without success. When running the same snippet on a ubuntu vm it works as expected.

[2]: screenshot 2014-09-21 14 01 28

sample

@linduxed
Copy link

Hi! This repository can be considered dead and will most likely not get any more development.

The reasoning behind this can be from this post onward and the repository of the fork can be read here.

btakita pushed a commit to btakita/rmagick that referenced this issue Jan 7, 2015
Fixed: test_from_blob(ImageList2_UT) in ImageList2.rb fails (on Windows)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants