
| Key: |
WTR-176
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Critical
|
| Assignee: |
Unassigned
|
| Reporter: |
Markus Kohler
|
| Votes: |
1
|
| Watchers: |
2
|
|
If you were logged in you would be able to see more operations.
|
|
|
Watir
Created: 01/Oct/07 07:20 AM
Updated: 24/Nov/08 02:04 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
1.5.2
|
| Fix Version/s: |
Soon
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
I changed one of the tests in attach_to_new_window_test.rb to :
def test_simply_attach_to_new_window
IE.attach_timeout = 0.2
100.times{
$ie.link(:text, 'New Window').click
ie_new = IE.attach(:title, //)
#assert(ie_new.text.include?('PASS'))
ie_new.close
}
end
and replaced the pass.html by a bigger html page.
Running this test with watir on windows shows that the IE process gets bigger and bigger, whereas running the same test manually doesn't show this behaviour.
I suspect that there's a memory leak in Watir, because I also see this problem in real world tests.
Regards,
Markus
|
|
Description
|
I changed one of the tests in attach_to_new_window_test.rb to :
def test_simply_attach_to_new_window
IE.attach_timeout = 0.2
100.times{
$ie.link(:text, 'New Window').click
ie_new = IE.attach(:title, //)
#assert(ie_new.text.include?('PASS'))
ie_new.close
}
end
and replaced the pass.html by a bigger html page.
Running this test with watir on windows shows that the IE process gets bigger and bigger, whereas running the same test manually doesn't show this behaviour.
I suspect that there's a memory leak in Watir, because I also see this problem in real world tests.
Regards,
Markus
|
Show » |
|