This project is archived and is in readonly mode.
Segmentation faults when profiling Rails 3 controllers using ruby-prof
Issue
ruby-prof produces segmentation faults when profiling Rails 3 controller actions that add new objects to the database using Ruby 1.9.2.
Troubleshooting/reduction
- Created new, empty Rails 3.0.3 project. Added one resource with no attributes, methods. Added profiling of 1000 creates of the resource in ItemsController#index action.
- Ran "rails server" using Ruby 1.9.2 p0. Loaded http://localhost:3000/items in browser. Server crashed with segmentation fault.
- Ran "rails server" using Ruby 1.8.7 p302. Loaded same URI. Action executed without issue.
- Repeated this test under different OS using same project files and Ruby 1.9.2 p0. Issue persisted.
System configuration
- Ruby 1.9.2 p0
- Rails 3.0.3
- ruby-prof 0.9.2
- Mac OS X 10.6.6
Additional
- Test case referred to in troubleshooting section attached
- Backtrace of segmentation fault crash attached
-
segfaulter.zip
118 KB
-
segfaulter_backtrace.txt
21.4 KB
-
rails- Tag changed from ruby 1.9.2, segfault crash, 3.0.3, active_record, bugs, profiling to ruby 192, segfault crash, 303, active_record, bugs, profiling
- State changed from new to open
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
rails
- State changed from open to stale