Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 526183 - Clear console on "Run as Eclipse Application" instance crashes IDE
Summary: Clear console on "Run as Eclipse Application" instance crashes IDE
Status: CLOSED DUPLICATE of bug 502711
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.6   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-17 22:26 EDT by Horacio Vico CLA
Modified: 2017-11-06 05:34 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Horacio Vico CLA 2017-10-17 22:26:27 EDT
This bug appeared since I upgraded to macOS Sierra, and it persists in High Sierra using differente versions of the IDE (now using 4.6.3).

Steps to reproduce:

1) Launch an Eclipse Plugin project by right click -> Run as -> Eclipse Application
2) A new Eclipse instance appears
3) Click the clear console icon in the Console tab
4) Eclipse crashes, stacktrace (at the first Eclipse instance console): 

!ENTRY org.jboss.ide.eclipse.as.core 4 16973826 2017-10-17 23:23:50.909
!MESSAGE The server was shutdown forcefully. All processes were terminated.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fff5c264470, pid=42392, tid=0x0000000000000307
#
# JRE version: Java(TM) SE Runtime Environment (8.0_102-b14) (build 1.8.0_102-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.102-b14 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# C  [libsystem_platform.dylib+0x1470]  _platform_memmove$VARIANT$Nehalem+0x70
#
# 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:
# /Users/hvico/Generador2015/eclipse-neon/Eclipse.app/Contents/MacOS/hs_err_pid42392.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

Apple Crash Report:

Process:               java [42392]
Path:                  /Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home/bin/java
Identifier:            java
Version:               1.0 (1.0)
Code Type:             X86-64 (Native)
Parent Process:        eclipse [40832]
Responsible:           java [42392]
User ID:               501

Date/Time:             2017-10-17 23:24:16.514 -0300
OS Version:            Mac OS X 10.13 (17A405)
Report Version:        12
Anonymous UUID:        64B61411-14B7-5252-C0C0-96102D784689

Sleep/Wake UUID:       ED23A9BD-C7F4-4E26-8287-5ED2C539CCD8

Time Awake Since Boot: 120000 seconds
Time Since Wake:       10000 seconds

System Integrity Protection: disabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGABRT)
Exception Codes:       KERN_INVALID_ADDRESS at 0x000000014de39184
Exception Note:        EXC_CORPSE_NOTIFY

VM Regions Near 0x14de39184:
    VM_ALLOCATE            000000014dbee000-000000014ddee000 [ 2048K] rw-/rwx SM=PRV  
--> 
    mapped file            000000014de40000-000000014de81000 [  260K] r--/r-x SM=ALI  

Application Specific Information:
abort() called


....
Comment 1 Patrik Suzzi CLA 2017-10-29 13:30:47 EDT
Cannot reproduce with Eclipse SDK
Version: Photon (4.8)
Build id: I20171028-1500
OS: Mac OS X, v.10.12.6, x86_64 / cocoa


Please, report this bug against JBoss IDE, as the first line of log suggests. 

!ENTRY org.jboss.ide.eclipse.as.core 4 16973826 2017-10-17 23:23:50.909


https://developer.jboss.org/wiki/HelpBugReport
Comment 2 Kondal Kolipaka CLA 2017-11-06 05:10:43 EST
This is fixed with the  https://bugs.eclipse.org/bugs/show_bug.cgi?id=502711

Fix is available from Eclipse 4.7 M7 onwards
Comment 3 Andrey Loskutov CLA 2017-11-06 05:34:45 EST

*** This bug has been marked as a duplicate of bug 502711 ***