This project is archived and is in readonly mode.
respond_to js with render :layout => false segfault
Reported by Luke van der Hoeven | March 1st, 2010 @ 08:59 PM | in 3.0.2
A little convoluted but I have the following code sequence.
JS/jQuery calls
$.get(uri + "/update_status", null, null, "script");
which is defined as:
def update_status
@sites = Site.all
PingWorker.async_ping_all_sites
respond_to do |format|
format.js { render :layout => false }
end
end
which is supposed to render
- @sites.each do |site|
- if site.status == "dead"
jQuery('#block#{site.id}').removeClass("green")
jQuery('#block#{site.id}').addClass("red")
- else
jQuery('#block#{site.id}').removeClass("red")
jQuery('#block#{site.id}').addClass("green")
Which in return, gives me a segfault and kills my Mongrel
instance.
I am using 3.0.0pre edge, ruby 1.9.1.
The only other thing I get is from firebug which shows a xml
response of:
XML Parsing Error: no element found Location:
moz-nullprincipal:{7a8e232a-7979-da44-8d55-22a592fcbfb5} Line
Number 1, Column 1:
^
Comments and changes to this ticket
-
Yehuda Katz (wycats) March 27th, 2010 @ 10:45 AM
- Milestone cleared.
- State changed from new to incomplete
What version of Ruby are you on?
-
José Valim April 7th, 2010 @ 12:51 AM
- State changed from incomplete to wontfix
Unfortunately, Ruby 1.9.1 has segfaults that were fixed only on 1.9.2. Please use 1.9.2-head in RVM. Thanks!
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>