Bug #4008

Rails 3::declarative_authorization::authorization_rules request => segvault ruby 1.9.2

Added by mike pusti almost 5 years ago. Updated over 1 year ago.

Status:Feedback
Priority:Normal
Assignee:Koichi Sasada
ruby -v:ruby 1.9.2p0 (2010-08-18 revision 29036) [x86_64-linux] Backport:

Description

I requested the route http://localhost:3000/authorization_rules of my Rails 3 project when the development server crashed.

http://github.com/stffn/declarative_authorization

Arch Linux( Kernel: 2.6.35-ARCH )
rvm 1.0.18

crash.log Magnifier - Logfile of the crash (rails s 2&> crash.log) (1.16 MB) mike pusti, 10/31/2010 08:49 PM

crash.log Magnifier - Logfile of the crash with libruby errors (rails s 2&> crash.log) (1.32 MB) mike pusti, 10/31/2010 08:59 PM

History

#1 Updated by mike pusti almost 5 years ago

It produces 2 different outputs

#2 Updated by Nobuyoshi Nakada almost 5 years ago

  • Priority changed from 5 to 3

It's infinite recurring, seems to fail to check if the SEGV is stack orverflow, but it's not always guaranteed.

#3 Updated by Yui NARUSE about 4 years ago

  • Status changed from Open to Assigned
  • Assignee set to Hiroshi Nakamura

#4 Updated by Hiroshi Nakamura about 4 years ago

  • Target version changed from 1.9.2 to 1.9.3

#5 Updated by Hiroshi Nakamura about 4 years ago

  • Assignee changed from Hiroshi Nakamura to Koichi Sasada

Here's a summary of crash.log: https://gist.github.com/1048296
As nobu said, infinite recursion should be the cause.

mike, would you please contact to declarative_authorization author for help?

Sasada-san, please close this ticket as 'Rejected(Not a bug)' if you're OK. I'm assigning you since I heard that you wanted to detect some kinds of infinite recursions as 'SystemStackError'. I don't know it's the one or not.

#6 Updated by Koichi Sasada about 4 years ago

  • Target version changed from 1.9.3 to 2.0.0

I send it to 1.9.x. (don't touch it before 1.9.3).

#7 Updated by Koichi Sasada about 3 years ago

  • Status changed from Assigned to Feedback

Could you try on current trunk?

#8 Updated by Koichi Sasada over 2 years ago

  • Target version changed from 2.0.0 to next minor

#9 Updated by Zachary Scott over 1 year ago

No feedback for over a year, should we close this?

#10 Updated by Nobuyoshi Nakada over 1 year ago

  • Description updated (diff)

Seems stack overflow, probably.
1.9.2 has died long ago, and there are many changes for it.
I think there is no chance for new release.

#11 Updated by Zachary Scott over 1 year ago

I am concerned about what Nahi said regarding infinite recursion handling. Also, after 2.0 Koichi asked for reproduce on trunk which makes me think he anticipates this issue > 1.9.2.

I'll leave this ticket for ko1 to determine whether or not it should be closed

Also available in: Atom PDF