Turns out that process crashes on my VM as well. I have downgraded to ruby 
1.9.2 where the problem does not exist. Still using watir 4.0.0.

Here is as much info as I can get on the process crash:

Source
Ruby interpreter (CUI) 1.9.3p194 [i386-mingw32]

Summary
Stopped working

Date
‎9/‎10/‎2012 10:16 a.m.

Status
Not reported

Description
Faulting Application Path:  c:\Ruby193\bin\ruby.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: ruby.exe
Application Version:  1.9.3.194
Application Timestamp:  4f92b949
Fault Module Name:  msvcrt-ruby191.dll
Fault Module Version: 1.9.3.194
Fault Module Timestamp: 4f92b948
Exception Code: c0000005
Exception Offset: 000545bc
OS Version: 6.1.7601.2.1.0.256.48
Locale ID:  5129
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789


Log Name:      Application
Source:        Application Error
Date:          9/10/2012 3:21:12 p.m.
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
Faulting application name: ruby.exe, version: 1.9.3.194, time stamp: 
0x4f92b949
Faulting module name: msvcrt-ruby191.dll, version: 1.9.3.194, time stamp: 
0x4f92b948
Exception code: 0xc0000005
Fault offset: 0x000545bc
Faulting process id: 0x1774
Faulting application start time: 0x01cda5c4bfa7424b
Faulting application path: c:\Ruby193\bin\ruby.exe
Faulting module path: c:\Ruby193\bin\msvcrt-ruby191.dll
Report Id: fde57235-11b7-11e2-bd32-782bcbb3a5b5
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event";>
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-10-09T02:21:12.000000000Z" />
    <EventRecordID>14212</EventRecordID>
    <Channel>Application</Channel>
    <Computer>YaelD990-PC.orion.internal</Computer>
    <Security />
  </System>
  <EventData>
    <Data>ruby.exe</Data>
    <Data>1.9.3.194</Data>
    <Data>4f92b949</Data>
    <Data>msvcrt-ruby191.dll</Data>
    <Data>1.9.3.194</Data>
    <Data>4f92b948</Data>
    <Data>c0000005</Data>
    <Data>000545bc</Data>
    <Data>1774</Data>
    <Data>01cda5c4bfa7424b</Data>
    <Data>c:\Ruby193\bin\ruby.exe</Data>
    <Data>c:\Ruby193\bin\msvcrt-ruby191.dll</Data>
    <Data>fde57235-11b7-11e2-bd32-782bcbb3a5b5</Data>
  </EventData>
</Event>

On Tuesday, 9 October 2012 10:19:04 UTC+13, Paul wrote:
>
> There is no stack dump or exception, all I get is the window I posted 
> which blocks execution untill I quit the window - nothing is given on the 
> command line. I suppose there might be some logs somewhere, I'll have a dig 
> around.
>
> On Tuesday, 9 October 2012 04:17:12 UTC+13, Jarmo Pertman wrote:
>>
>> What is the exact crash message when you run the command printed out by 
>> $DEBUG on your command line?
>>
>> Jarmo Pertman
>> -----
>> IT does really matter - http://itreallymatters.net
>>
>>
>> On Monday, October 8, 2012 6:36:41 AM UTC+3, Paul wrote:
>>>
>>> Ok, does no crash on my VM so its something to do with my PC environment.
>>>
>>> On Monday, 8 October 2012 16:17:00 UTC+13, Paul wrote:
>>>>
>>>> I see now that click_no_wait is run from method_missing in element.rb.
>>>>
>>>> I turned on DEBUG, grabbed the spawned process command and ran it at 
>>>> the command prompt.
>>>>
>>>> ruby -e 
>>>> "$:.unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/watir-classic-3.2.0/lib/watir-classic/win32ole/1.9.3').unshift('C:\\Users\\pauld\\workspace\\SopranoMedicalRecords\\AutomatedTests\\med_rec\\').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/ffi-1.1.5-x86-mingw32/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/win32-process-0.7.0/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/win32-api-1.4.8-x86-mingw32/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/windows-api-0.4.2/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/windows-pr-1.2.2/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/nokogiri-1.5.5-x86-mingw32/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/rautomation-0.7.2/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/xml-simple-1.1.1/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/rake-0.9.2.2/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/hoe-3.1.0/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/s4t-utils-1.0.4/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/builder-3.1.3/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/user-choices-1.1.6.1/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/yajl-ruby-1.1.0-x86-mingw32/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/subexec-0.0.4/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/mini_magick-3.2.1/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/win32screenshot-1.0.7/lib').unshift('c:/Ruby193/lib/ruby/gems/1.9.1/gems/watir-classic-3.2.0/lib').unshift('c:/Ruby193/lib/ruby/site_ruby/1.9.1').unshift('c:/Ruby193/lib/ruby/site_ruby/1.9.1/i386-msvcrt').unshift('c:/Ruby193/lib/ruby/site_ruby').unshift('c:/Ruby193/lib/ruby/vendor_ruby/1.9.1').unshift('c:/Ruby193/lib/ruby/vendor_ruby/1.9.1/i386-msvcrt').unshift('c:/Ruby193/lib/ruby/vendor_ruby').unshift('c:/Ruby193/lib/ruby/1.9.1').unshift('c:/Ruby193/lib/ruby/1.9.1/i386-mingw32');require
>>>>  
>>>> 'c:/Ruby193/lib/ruby/gems/1.9.1/gems/watir-classic-3.2.0/lib/watir-classic/core';Watir::Button.new(Watir::IE.attach(:hwnd,
>>>>  
>>>> 922786).frame({:tag_name=>['frame', 'iframe'], :id=>'viewIFRAME'}), 
>>>> :tag_name => Array.new << 'button' << 'submit' << 'image' << 'reset', 
>>>> :unique_number => 1).click!();"
>>>>
>>>>
>>>>
>>>> Again so we can see all the info:
>>>>
>>>>
>>>>
>>>>
>>>> Looks like that process is crashing. Anyone else have that problem? 
>>>> Maybe it is something with my environment - will set up a VM and try that.
>>>>
>>>> I will keep debugging this, it is crucial I solve this. I am handing 
>>>> over the framework I wrote to my collegues as I start a new job next week.
>>>>
>>>> Any help is appreciated.
>>>>
>>>> On Friday, 5 October 2012 09:52:31 UTC+13, Paul wrote:
>>>>>
>>>>> Hi, I have just upgraded my framework to 1.9.3 and watir 4.0, I am 
>>>>> using watir-classic 3.2.0. I have been using click_no_wait but now it 
>>>>> does 
>>>>> not work and I can't find the method in the source. element.rb no longer 
>>>>> has this method!
>>>>>
>>>>> If I can't solve this I will try to patch it in or downgrade watir.
>>>>>
>>>>> - thanks
>>>>>
>>>>

-- 
Before posting, please read http://watir.com/support. In short: search before 
you ask, be nice.

[email protected]
http://groups.google.com/group/watir-general
[email protected]

Reply via email to