Project

General

Profile

Actions

Bug #5756

closed

crashs when Twitter.update_with_media with rails

Added by paranoiase (SungHee Kang) over 12 years ago. Updated about 11 years ago.

Status:
Rejected
Target version:
-
ruby -v:
ruby 1.9.3dev (2011-09-23 revision 33323) [x86_64-darwin10.6.0]
Backport:
[ruby-core:41626]

Description

I'm using the Ruby 1.9.3dev and Ruby on Rails 3.1.3
When I use twitter gem and call 'Twitter.update_with_media', the interpreter crashs.

~~ ruby
class WelcomeController < ApplicationController
def upload
Twitter.update_with_media("I'm tweeting with gem!", File.new('screenshot.png'))
end
~~

it doesn't crash when I use 1.9.2. or 1.9.3dev without rails.
You can reproduse this situation to

  1. create new rails 3.1.3 projects
  2. add gem 'twitter' in your Gemfile
  3. configure twitter consumer key, secret and oauth token, secret in your config/initializers
  4. make the action WelcomeController#upload and route it to POST /upload
  5. run the server and access POST /upload

Files

crashog.txt (61.3 KB) crashog.txt The crash log paranoiase (SungHee Kang), 12/13/2011 03:55 PM
crash.log (129 KB) crash.log paranoiase (SungHee Kang), 12/14/2011 04:59 PM
crash_macos.log (15.1 KB) crash_macos.log paranoiase (SungHee Kang), 12/14/2011 08:56 PM

Updated by sorah (Sorah Fukumori) over 12 years ago

  • Status changed from Open to Feedback
  • please upload full of log; your uploaded "crashog.txt" seems partial.
  • "ruby -v" is not output of ruby -v; please paste exact output of "ruby -v" like this: ruby 2.0.0dev (2011-11-25 trunk 33837) [x86_64-darwin11.2.0]

thanks.

Updated by paranoiase (SungHee Kang) over 12 years ago

I can't upload full logs because it's too long. It was rendered only 600 lines.
'ruby -v' is ruby 1.9.3dev (2011-09-23 revision 33323) [x86_64-darwin10.6.0]

best regards.

Updated by sorah (Sorah Fukumori) over 12 years ago

  • ruby -v changed from 1.9.3.dev to ruby 1.9.3dev (2011-09-23 revision 33323) [x86_64-darwin10.6.0]

take a log doing like this: ruby aaa.rb|&tee crash.log or ruby aaa.rb 2>&1 >crash.log

Updated by paranoiase (SungHee Kang) over 12 years ago

Thanks. But how can I do this on rails?

Updated by paranoiase (SungHee Kang) over 12 years ago

Got It! I changed the iTerm scrollback status to unlimited then I should take a full log.

Best regards.

Updated by sorah (Sorah Fukumori) over 12 years ago

SungHee Kang wrote:

Thanks. But how can I do this on rails?

Simply do `rails something|&teeā€¦ :-)

If you're using OSX, please upload a crash log generated by OS X
See: http://bugs.ruby-lang.org/projects/ruby/wiki/HowToReport#Simple-steps

If Ruby crashed on OS X, you should have a crashlog under ~/Library/Logs/CrashReporter or /Library/Logs/CrashReporter. You should paste or attach it if available.

Updated by paranoiase (SungHee Kang) over 12 years ago

Thanks for the response. I will attach the crash log for MacOS.

Actions #8

Updated by mame (Yusuke Endoh) over 11 years ago

  • Status changed from Feedback to Assigned
  • Assignee set to sorah (Sorah Fukumori)

OP provided a feedback. Sorah, please check it.

--
Yusuke Endoh

Updated by sorah (Sorah Fukumori) over 11 years ago

  • Status changed from Assigned to Feedback

seems crashing on openssl. please try building ruby again with openssl NOT COMES WITH OS X (building by your hand, including using homebrew or macports or some)

Updated by drbrain (Eric Hodel) about 11 years ago

  • Status changed from Feedback to Rejected

No response from the submitter after a feedback request so I am rejecting this.

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0