Bug 563437 - handling of stack overflow exceptions
Summary: handling of stack overflow exceptions
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.7   Edit
Hardware: All Windows 10
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-21 13:01 EDT by Dave Dyer CLA
Modified: 2020-05-22 01:33 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Dyer CLA 2020-05-21 13:01:58 EDT 
When the current thread exception is StackOverflowException, eclipse basically
never finishes preparing the display of thread state. Presumably it is preparing
a detailed stack trace with millions of steps....   The only way I've found to cope
with this is to redo with an artifically small stack allocation.     Eclipse ought to
cope with this situation better - perhaps lazy evaluation of the stack trace would
be better in all cases, and would solve the problem for all threads with a deep
stack, not just those that overflow.

-- Configuration Details --
Product: Eclipse 4.7.3.20180405-1200 (org.eclipse.epp.package.java.product)Installed Features:
 org.eclipse.platform 4.7.3.v20180330-0640
Comment 1 Sarika Sinha CLA 2020-05-22 00:19:29 EDT 
Can you give a sample test case with steps?
Comment 2 Dave Dyer CLA 2020-05-22 01:33:55 EDT 
(rolling my eyes) try this

public class overflow {

	public static void recurser(int n)
	{
		recurser(n-1);
	}
	public static void main(String args[])
	{
		recurser(1000000000);
	}
}