Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3603290
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T20:51:14+00:00 2026-05-18T20:51:14+00:00

Running either alone works fine, but when running both together, it crashes hard, at

  • 0

Running either alone works fine, but when running both together, it crashes hard, at what seems like Magick::Image#new (the first call I make to it).

Edit: Request for code fulfilled below:

Under Ramaze, the issue can be reproduced like this

require 'ramaze'
require 'rmagick'

class ExceptionCauser < Ramaze::Controller
map '/'

  def index
    img = Magick::Image.new(64, 64)
  end

end

Ramaze.start :port => 7004

and then visiting 0.0.0.0:7004 will crash.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-18T20:51:14+00:00Added an answer on May 18, 2026 at 8:51 pm

    Can be fixed by recompiling Imagemagick using the --disable-openmp flag, as in Why is this RMagick call generating a segmentation fault? .

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

On a daily basis I: use multiple workstations running either Linux, Windows, or MacOS
I have a batch file that is running inside CruiseControl and outputing either Pass
I need to either bring front browser window if it is already running or
I've been struggling along with sockets, making OK progress, but I keep running into
This question should be quite clear from its title alone, but let me explain
Running into a problem. I have a table defined to hold the values of
-- Running within ASP.NET MVC alongside jQuery -- I'm using jQuery to render a
Running the static analyzer on this piece of code: - (id) readForeignPref { CFPropertyListRef
Running PHP under IIS on my Win XP Pro system. I cannot debug my
Running the following vbscript to call svnadmin dump fails (i.e. no dump is being

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.