Project

General

Profile

Actions
Copy link

Bug #4008

closed

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

Bug #4008: Rails 3::declarative_authorization::authorization_rules request => segvault ruby 1.9.2

Added by Feanor (mike pusti) about 15 years ago. Updated over 8 years ago.

Status:
Closed
Assignee:
ko1 (Koichi Sasada)
Target version:
2.6
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

Files

Download all files
crash.log (1.16 MB) crash.log Logfile of the crash (rails s 2&> crash.log) Feanor (mike pusti), 10/31/2010 08:49 PM
crash.log (1.32 MB) crash.log Logfile of the crash with libruby errors (rails s 2&> crash.log) Feanor (mike pusti), 10/31/2010 08:59 PM

Updated by Feanor (mike pusti) about 15 years ago Actions
Copy link
 #1

It produces 2 different outputs

Updated by nobu (Nobuyoshi Nakada) almost 15 years ago Actions
Copy link
 #2

  • 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.

Updated by naruse (Yui NARUSE) over 14 years ago Actions
Copy link
 #3 [ruby-core:37424]

  • Status changed from Open to Assigned
  • Assignee set to nahi (Hiroshi Nakamura)

Updated by nahi (Hiroshi Nakamura) over 14 years ago Actions
Copy link
 #4

  • Target version changed from 1.9.2 to 1.9.3

Updated by nahi (Hiroshi Nakamura) over 14 years ago Actions
Copy link
 #5 [ruby-core:37557]

  • Assignee changed from nahi (Hiroshi Nakamura) to ko1 (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.

Updated by ko1 (Koichi Sasada) over 14 years ago Actions
Copy link
 #6 [ruby-core:37954]

  • 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).

Updated by ko1 (Koichi Sasada) over 13 years ago Actions
Copy link
 #7 [ruby-core:45850]

  • Status changed from Assigned to Feedback

Could you try on current trunk?

Updated by ko1 (Koichi Sasada) almost 13 years ago Actions
Copy link
 #8 [ruby-core:50117]

  • Target version changed from 2.0.0 to 2.6

Updated by zzak (zzak _) over 11 years ago Actions
Copy link
 #9 [ruby-core:61540]

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

Updated by nobu (Nobuyoshi Nakada) over 11 years ago Actions
Copy link
 #10 [ruby-core:61549]

  • 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.

Updated by zzak (zzak _) over 11 years ago Actions
Copy link
 #11 [ruby-core:61551]

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

Updated by ko1 (Koichi Sasada) over 8 years ago Actions
Copy link
 #12 [ruby-core:79342]

  • Status changed from Feedback to Closed

Sorry I didn't check it.
Please reopen this ticket if someone has trouble yet.

Actions
Copy link

Also available in: PDF Atom