Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 522231

Summary: Stackoverflow in RecoveredBlock.updatedBlock.
Product: [Eclipse Project] JDT Reporter: chou ching <zhouqing567>
Component: CoreAssignee: Project inbox <recommenders-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: major    
Priority: P3    
Version: 4.7   
Target Milestone: ---   
Hardware: PC   
OS: Windows 10   
Whiteboard: stalebug

Description chou ching CLA 2017-09-13 05:26:33 EDT
What steps will reproduce the problem?
1. this snippet cause the problem
   tableColumnAncestor.setCellFactory(param -> new TableCell<TableTestObject, TableTestObject>() {
            @Override
            protected void updateItem(TableTestObject item, boolean empty) {
                super.updateItem(item, empty);
                if (empty) {
                    setText(null);
                } else {
                    ComboBox<String> cb = new ComboBox<>(ancestorList);
                    cb.getSelectionModel().selectedItemProperty().addListener((ChangeListener<String>) (observable, oldValue, newValue) -> {
                        item.ancestorProperty().set(newValue);
                        System.out.println(item.descendantProperty().get());
                    });
                    setGraphic(cb);
                    setContentDisplay(ContentDisplay.GRAPHIC_ONLY);
                }
            }
        });
2. 
3. 


-- Error Details --
Date: Wed Sep 13 16:27:39 CST 2017
Message: Session processor ‘class org.eclipse.recommenders.internal.calls.rcp.CallCompletionSessionProcessor’ failed with exception.
Severity: Error
Product: Eclipse 4.7.0.20170620-1800 (org.eclipse.epp.package.jee.product)
Plugin: org.eclipse.recommenders.completion.rcp
Session Data:
eclipse.buildId=4.7.0.I20170612-0950
java.version=1.8.0_101
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=zh_TW
Framework arguments:  -product org.eclipse.epp.package.jee.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product

Exception Stack Trace:
java.lang.StackOverflowError
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedStatement(RecoveredBlock.java:387)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedBlock(RecoveredBlock.java:332)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedStatement(RecoveredBlock.java:387)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedBlock(RecoveredBlock.java:332)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedStatement(RecoveredBlock.java:387)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedBlock(RecoveredBlock.java:332)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedStatement(RecoveredBlock.java:387)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedBlock(RecoveredBlock.java:332)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedStatement(RecoveredBlock.java:387)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedBlock(RecoveredBlock.java:332)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedStatement(RecoveredBlock.java:387)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedBlock(RecoveredBlock.java:332)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedStatement(RecoveredBlock.java:387)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedBlock(RecoveredBlock.java:332)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedStatement(RecoveredBlock.java:387)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedBlock(RecoveredBlock.java:332)
	at org.eclipse.jdt.internal.compiler.parser.RecoveredBlock.updatedStatement(RecoveredBlock.java:387)
Comment 1 Eclipse Genie CLA 2020-01-10 15:14:35 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.