search

robotframework / RIDE

Test data editor for Robot Framework
Apache License 2.0
958 stars 378 forks source link

RIDE sometimes hangs up while google chrome is running #749

Closed yanne closed 9 years ago

yanne commented 9 years ago

Originally submitted to Google Code by icts... on 21 Feb 2011

Robot Framework 2.5.5 (Python 2.6.4 on win32)

I use RIDE 0.32.1 and have noticed that it sometimes hangs up while Google Chrome (ver. 11.0.672.2 dev) is running. After a while I found that closing Chrome return RIDE to normal work. It's strange that browser may affect RIDE.

yanne commented 9 years ago

Originally submitted to Google Code by @mkorpela on 21 Feb 2011

Thanks for the defect report!

Could you explain in more detail what was happening?

Did you have some logs/reports open in Chrome? Were you running tests through RIDE that use Chrome?

yanne commented 9 years ago

Originally submitted to Google Code by icts... on 21 Feb 2011

It is not matter have I opened reports or logs in Chrome. It can be just started. I run tests through RIDE but, it does not use Chrome at all. I use it only to view reports and logs.

It happens when I navigate through tests tree to edit a test case using mouse. I click on a test case and RIDE stop responding and become working only if I close Chrome.

yanne commented 9 years ago

Originally submitted to Google Code by @mkorpela on 4 Mar 2011

Could you check the memory usage of Chrome and RIDE processes?

yanne commented 9 years ago

Originally submitted to Google Code by rucind... on 17 Mar 2011

I have also noticed this issue. Here are more details:

I am using Google Chrome 10.0.648.134 beta. I have RobotFramework 2.5.6 installed and I have tried RIDE 0.33.

If I have Chrome running and I open RIDE, right after I load a test suite in RIDE, both Chrome and RIDE become unresponsive. This happens for me every time, so it's not a random issue.

I have tried installing RIDE 0.32.1, 0.32, 0.31 - all have the same issue.

However, if I use RIDE 0.30, there are no problems whatsoever - except that I don't get the cool new features :)

The easiest way to reproduce the problem with Chrome becoming unresponsive is to:

  1. Have Chrome running.
  2. Run RIDE.
  3. Load a test suite - this might load right away or take a really long time.
  4. Go to Chrome while RIDE is running or loading the suite and open a new tab.

At this point, the whole Chrome window turns "full screen", displaying a blank/white page and becomes unresponsive. RIDE is unresponsive as well.

I'd be happy to give more info if needed, please just let me know what would help.

yanne commented 9 years ago

Originally submitted to Google Code by @jrantanen on 18 Mar 2011

We can reproduce the issue with Windows 7, what is your operating system?

yanne commented 9 years ago

Originally submitted to Google Code by @spooning on 18 Mar 2011

Happens since revision 48e77d4704e5

yanne commented 9 years ago

Originally submitted to Google Code by @spooning on 18 Mar 2011

So far we have only reproduced this very odd bug with: Win 7 (64 bit) Python 2.7 (64 bit) wxPython (2.8.11 and 2.9.1.1) Google Chrome (10.0.648.151)

yanne commented 9 years ago

Originally submitted to Google Code by @mkorpela on 19 Mar 2011

I'm studying the issue but I think it is unlikely that we can fix this in Ride directly as it is related to operating system and a 3rd party application.

yanne commented 9 years ago

Originally submitted to Google Code by @mkorpela on 19 Mar 2011

Posted an issue to chromium issue tracker: https://code.google.com/p/chromium/issues/detail?id=76800 and also to help forum: http://www.google.com/support/forum/p/Chrome/thread?tid=37edfc6e8a656b9a&hl=en

yanne commented 9 years ago

Originally submitted to Google Code by @mkorpela on 21 Mar 2011

Make a mini-application that does this.

yanne commented 9 years ago

Originally submitted to Google Code by cristoph... on 26 May 2011

I am seeing the same behavior (RIDE hangs up), this is my setup in case it helps:

Win 7 (64 bit) Python 2.6.4 (64 bit) wxPython (2.8.10) Google Chrome (11.0.696.68) Ride 0.35.1 Robot Framework 2.5.7

The way to reproduce it is the same as explained in above posts.

yanne commented 9 years ago

Originally submitted to Google Code by @mkorpela on 26 May 2011

If you want this fixed please Upvote the issue in chromium issue tracker! There is currently over 25000 open issues in the tracker.

https://code.google.com/p/chromium/issues/detail?id=76800

yanne commented 9 years ago

Originally submitted to Google Code by @pekkaklarck on 11 Jul 2011

Issue 825 has been merged into this issue.

yanne commented 9 years ago

Originally submitted to Google Code by aborichev on 11 Oct 2011

I've faced with this issue recently, once I've updated Chrome to the latest version 14.0.835.202 m. Unfortunately I haven't stored previous version of Chrome.

Issue is reproduced mostly when there is robotframework report/log opened in Chrome. If I close all logs/reports in Chrome, issue is not reproduced (at least at my configuration).

Win7(64 bit) Robotframework 2.6.2. RIDE 0.39.1

yanne commented 9 years ago

Originally submitted to Google Code by fionna.o... on 23 Oct 2011

I am seeing this with following config:

Windows 7 64-bit Python: 2.7.2 wxpython: 2.8.12.1 RIDE: Version 0.39.1 running on Python 2.7.2 using Robot Framework trunk 20110925. Chrome: 14.0.835.202 m

Chrome only seems to crash if a report or log is open. RIDE resumes immediately when Chrome is closed. (Have upvoted issue in chromium tracker too)

yanne commented 9 years ago

Originally submitted to Google Code by r... on 24 Oct 2011

I can reproduce with same specs as previous poster: Windows 7 64-bit Python 2.7.2 64-bit wxPython 2.8.12.1 64-bit RIDE 0.39.1 Chrome 14.0.835.202 m

For what it's worth, I do NOT always reproduce it when a Robot log/report are open. It's possible that the correlation other posters are seeing has more to do with the Chrome resources those logs/reports require (they can be enormous HTML documents) than the fact that they happen to be a Robot log/report. Just an idea.

yanne commented 9 years ago

Originally submitted to Google Code by gauravsw... on 12 Jan 2012

RIDE always hangs for me whenever I open a new tsv file. Shutting down chrome opens the test case within seconds.

I can reproduce with these specs: Windows 7 64-bit Python 2.7.2 64-bit wxPython 2.8.12.1 64-bit RIDE 0.40.1 Chrome 16.0.912.75 m

yanne commented 9 years ago

Originally submitted to Google Code by aashish.... on 12 Jan 2012

I am also not able to open any test file in RIDE, with google chrome running. Shutting down chrome makes RIDE responsive.

My specs are: Windows 7 64-bit Python 2.7.2 64-bit wxPython 2.8.12.1 64-bit RIDE 0.40.1 Chrome 16.0.912.75 m

yanne commented 9 years ago

Originally submitted to Google Code by @mkorpela on 12 Jan 2012

I can still reproduce the problem (but it is flickering).

yanne commented 9 years ago

Originally submitted to Google Code by cdekter on 19 Jan 2012

I don't think Chrome is the root cause. I get this problem without Chrome even installed on the machine. Haven't been able to identify any other cause however.

yanne commented 9 years ago

Originally submitted to Google Code by jmitche... on 19 Jan 2012

It definitely possible that it can occur without Chrome. However I use RIDE and Chrome every day and I'm certain of the interaction! RIDE locks up from time to time, and then consistently unlocks as soon as I close Chrome.

yanne commented 9 years ago

Originally submitted to Google Code by noz.mor... on 22 Jan 2012

I am also not able to open any test file in RIDE, with google chrome running but not only. I have find out that another program makes RIDE unresponsive too.

Logitech Scroll App (http://goo.gl/5u5rT) The Scroll App is a software plug-in that provides a smooth-scrolling experience for web browsing.

Shutting down programs makes RIDE responsive.

Windows 7 64-bit

Python 2.7.2 wxPython 2.8.12.1 RIDE 0.40.2 (tried x32 and x64 - the same)

Chrome 16.0.912.75 Logitech Scroll App 3.00.31

P.S.: I have got a BSOD twice when RIDE was hanging. In future I will present a full log.

yanne commented 9 years ago

Originally submitted to Google Code by @mkorpela on 10 Feb 2012

Most likely fixed in https://github.com/robotframework/RIDE/commit/5b6ce8cdc6fa27ebd40df83709c45f92347d2edf

needs more testing.

Here is the miniapplication that reproduces the problem with wxpython in 64bit windows 7: https://gist.github.com/1779779

yanne commented 9 years ago

Originally submitted to Google Code by @mkorpela on 13 Feb 2012

Seems to work..