#89 ✓hold
Kieran P

Excessive output caused by (and only by) running Webrat

Reported by Kieran P | December 10th, 2008 @ 03:25 PM

Webrat is the only thing that causes this. It doesn't affect the testing, but it's a lot of useless debug info/ruby warnings that clog the output. Would be nice if it didn't do this.

$ ruby -v ruby 1.8.6 (2008-08-08 patchlevel 286) [i686-darwin9.5.0]
$ ls /opt local ruby-enterprise-1.8.6-20081205

Using latest REE on Mac Leopard.


Loaded suite /opt/ruby-enterprise-1.8.6-20081205/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake/rake_test_loader
Started
ruby(918) malloc: *** error for object 0x1f537a8: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug ruby(918) malloc: *** error for object 0x1f53428: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug .ruby(918) malloc: *** error for object 0x378ccb0: Non-aligned pointer being freed (2) *** set a breakpoint in malloc_error_break to debug ruby(918) malloc: *** error for object 0x378cce8: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug .ruby(918) malloc: *** error for object 0x2286268: Non-aligned pointer being freed *** set a breakpoint in malloc_error_break to debug ruby(918) malloc: *** error for object 0x2286d90: Non-aligned pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug .ruby(918) malloc: *** error for object 0x375c3b8: Non-aligned pointer being freed *** set a breakpoint in malloc_error_break to debug ruby(918) malloc: *** error for object 0x375c380: Non-aligned pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug ruby(918) malloc: *** error for object 0x20e9380: Non-aligned pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug ruby(918) malloc: *** error for object 0x20e9188: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug ruby(918) malloc: *** error for object 0x20e9f50: Non-aligned pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug .ruby(918) malloc: *** error for object 0x3588cb0: Non-aligned pointer being freed (2) *** set a breakpoint in malloc_error_break to debug ruby(918) malloc: *** error for object 0x3588460: Non-aligned pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug .ruby(918) malloc: *** error for object 0x22cc348: Non-aligned pointer being freed *** set a breakpoint in malloc_error_break to debug ruby(918) malloc: *** error for object 0x22cca10: Non-aligned pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug visits is deprecated. Use visit instead.
.ruby(918) malloc: *** error for object 0x3637d58: Non-aligned pointer being freed *** set a breakpoint in malloc_error_break to debug ruby(918) malloc: *** error for object 0x3637038: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug visits is deprecated. Use visit instead.
selects is deprecated. Use select instead.
clicks_button is deprecated. Use click_button instead.
selects is deprecated. Use select instead.
clicks_button is deprecated. Use click_button instead.
ruby(918) malloc: *** error for object 0x2e248c0: Non-aligned pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug ruby(918) malloc: *** error for object 0x2e24268: Non-aligned pointer being freed
*** set a breakpoint in malloc_error_break to debug ruby(918) malloc: *** error for object 0x2e242a0: Non-aligned pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug .ruby(918) malloc: *** error for object 0x1f53bd0: Non-aligned pointer being freed (2) *** set a breakpoint in malloc_error_break to debug ruby(918) malloc: *** error for object 0x1f53930: Non-aligned pointer being freed (2)
*** set a breakpoint in malloc_error_break to debug . Finished in 17.629958 seconds.

Comments and changes to this ticket

  • Bryan Helmkamp

    Bryan Helmkamp December 27th, 2008 @ 03:09 PM

    • State changed from “new” to “hold”

    I suspect this might be a Nokogiri issue. Webrat doesn't use any C-extensions itself, so I don't think it would be generating those sorts of warnings.

    Can you upgrade to the latest Nokogiri (1.1.0, I think) and Webrat see if this is still an issue?

    Thanks,

    -Bryan

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Ruby Acceptance Testing for Web applications.

Shared Ticket Bins

People watching this ticket

Pages