[John]

We are seeing an intermittent browser crash on reload. intermittent from day to day. sometimes crash will occur every other reload sometimes 2 or 3 times per day.

CONFIGURATIONS:
* Win 7
* Win 10
* Chrome 60.0.3112.113 (Official Build) (64-bit)
* CI8 – Prerelease

Reproduction steps:
* launch browser with/without debug through webclipse
Cannot be reliably reproduced

NOTE
Issue is SIGNIFICANTLY reduced when launching browser externally. I have confirmed both browser show same version info.

IMPACT
Can be quite high when launching from eclipse. Issue is very minor when launching externally (we do not use weblive or single step debug very often).

• This topic was modified 7 years, 2 months ago by John.

[support-swapna]

Lamar,

Sorry that you are seeing this issue.

Can you please give us some more details?

1. Please share with us the .log file located at workspace dir/.metadata/.log for further investigation.

2. Do you see the problem when reloading the angular app in the browser or with any project like web project as well?

3. Do you remember seeing the crash problem with previous build or does it happen only after updating to the CI 8 prerelease build?

4. Can you please let us know what exact steps you are following i.e the kind of changes you are making to the code or the project and reloading the browser?

5. What are the symptoms of the crash? Does the browser just close/disappear without any error/warning dialog or any reference to a crash file? Please elaborate what exactly happens when you reload the browser.

Apologies for inconvenience caused.

–Swapna
MyEclipse Support

[John]

I was able to duplicate the issue this morning and collect 2 logs (attached).

2. I only see this when reloading a web project in eclipse. Only when browser is launched from Eclipse.

3. This is not new to pre-release. Has been with us for several releases. Duplicated on 2 installations (different WIn7/Win10)

4. Changes to code seem irrelevant. Simply make changes (any changes) and save triggering auto-reload.

5. Crash is browser freeze with high memory utilization. Browser must be stopped externally

Thanks,
-Lamar

• This reply was modified 7 years, 2 months ago by John.

Attachments:

You must be logged in to view attached files.

[support-swapna]

Lamar,

Thank you for the details and the log files.

Can you please check if the ‘CodeLive’ is enabled for the server in the Servers view?
If yes, then please disable ‘CodeLive’ for the server, delete the contents of the .log file and check if you can still replicate the problem with the browser crash.

For help with disabling CodeLive, please refer to this tutorial : https://www.genuitec.com/docs/web-apps/modern-web/using-codelive-for-angular/

If disabling CodeLive does not help and the issue persists, then please send us the .log file for further investigation. Please share with us the server and its version details.

Also let us know if you have installed any third party plugins related to web projects.

–Swapna
MyEclipse Support

[John]

Issue occurs with code live enabled or disabled
no 3rd party plugins or apps

[Brian Fernandes]

John,

Thank you for those details. We’re at a bit of a loss because we’re unable to reproduce the problem here, and I wonder if may have something to do with your app – since you mentioned it crashes when Chrome is externally launched as well, albeit far less frequently.

1) Any difference with the latest version of Chrome? We tried with the version you specified, but I notice that a more recent version is now available.
2) Would it be possible to try a default Angular app and see if you can reproduce the problem there too? Just use the Angular Project wizard to create a new Angular project with the defaults, and serve this one. Try debugging this and making some changes a few times.
3) I’d like to specifically clarify your answer to a question asked earlier – whether this happens for Angular projects or Web projects, to which you said “Web projects”. By any chance, is your project a Java EE project (technically called “Web Projects in Eclipse) containing Angular bits, or is it just an Angular project? How did you create it?
4) As far as the error logs you shared earlier are concerned – do you mind clearing your log (from the error log view) and then reproducing the error and sharing that log? The logs shared earlier cover a rather large period so it’s difficult to co-relate with the crash.
5) From your previous posts, you’ve stated that the errors occur on automatic reload. It might be interesting to refresh the browser manually (outside of a change cycle) to see if that causes the crash as well. When it does happen as part of an automatic reload – anything out of the ordinary listed in the Terminal view?

Thanks!

[John]

I haven’t any seen crashes when launching the browser externally since the last release/pre-release.

I confirmed it still crashes when launched from eclipse.

[Brian Fernandes]

John,

Thanks for the update. I have a few additional questions (I still do need the questions from my previous post answered).

6) When you reproduce the issue, can you go to the Debug view within Eclipse, click on the debug session node and then terminate? This will terminate the debug session – by any chance does Chrome recover?
7) Go to Window > Preferences > JavaScript > Debug > Browser Location – this should point to chrome.exe – anything odd about the path? You stated that both Chrome instances did display the same version, but they could still be different installs.
8) How exactly are you launch the app with/without a Debug connection – do you use the Run As / Debug As context menu actions on the app? When testing with an external browser, what action do you take within the IDE to serve the app (and not open the browser)?

I know we’re asking for a lot of information, hopefully there will be some clues in there as to why the browser is crashing.

Thanks!

[John]

Sorry for the delay. We are typically launching externally due to this bug and haven’t seen crashes since last update.

We have seen this across multiple projects.

6) we have no debug session active (we rarely use single step debugging)
7) Browser location is same as that in desktop launch. Additionally same under the servers tab (I’m sure it is same info). Additional settings:
* disable browser cache
* Enable source map support
* Hot-swap enabled

8) shortcut on Windows taskbar
Target: “C:\Program Files (x86)\Google\Chrome\Application\chrome.exe”
Start In: “C:\Program Files (x86)\Google\Chrome\Application”

(same as preferences, all default. no compat settings)

new crash log attached

Attachments:

You must be logged in to view attached files.

[Author]

Posts