You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On linux, after the deployment of a GAE/GWT application (simple project generated via GPE's new web application feature) finished, and Eclipse tries to open the browser with the url of the app an segfault happens:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fc16ed69eaf, pid=27204, tid=27280
#
# JRE version: OpenJDK Runtime Environment (8.0) (build 1.8.0-google-v7-114555630-114530017)
# Java VM: OpenJDK 64-Bit Server VM (25.51-b03 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libgdk-x11-2.0.so.0+0x4ceaf] gdk_display_open+0x3f
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /tmp/gpe45_testing/eclipse-mars-upgradelorry/hs_err_pid27204.log
#
# If you would like to submit a bug report, please visit:
# http://b.corp.google.com/createIssue?component=32554
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Most of the code just wraps each build step in a ListenableFuture. The inputs to each build step then become the ListenableFutures for their dependencies (the steps they depend on).
The code should be refactored to reduce the mess of ListenableFutures everywhere.
On linux, after the deployment of a GAE/GWT application (simple project generated via GPE's new web application feature) finished, and Eclipse tries to open the browser with the url of the app an segfault happens:
If the checkbox to open the app in browser after deploy (in the GPE deploy dialog) is cleared, the app deploys successfully, and Eclipse does not crash.
Possibly related:
Sloeber/arduino-eclipse-plugin#397
https://bugs.eclipse.org/bugs/show_bug.cgi?id=430736
The text was updated successfully, but these errors were encountered: