But the connection for debugging is obviously lost (no console output in IntelliJ, no "active" symbol for breakpoints. The browser loads the correct page when copying the URL from the debug configuration into the adress bar. After that I renamed the profile directory and it was recreated after the next launch without any complaints - but still not opening the intended URL.) That triggered an dialog to get feedback to Google, so I told them about it. (It claimed that "the crrent profile version is newer than supported by the browser". On the next try to launch it had an issue with the profile version. I checked the Chrome version and updated it to the newest version (now. issues or crashes, leading to a 20 reduction in the number of tickets. It worked with an earlier version of IntelliJ IDEA before the holidays (already with the new "don't need no Chrome extension anymore" feature), but now, if I start the debug configuration the chrome window does only show "about:blank" in the adress bar, not the intended URL. The official ioGround proxy is a Chrome Extension that can be used to unblock. But this is the first suitable entry when searching for this issue, so I give it a try. I'm not sure if I should revive this thread or file a bug report, but I'm seeing this issue now with IntelliJ IDEA 2017.3.2. If your computer runs out of memory while youre using Chrome, Chrome will likely freeze and/or crash.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |