Bug 372465

Summary:	Launch Configuration changes are not saved
Product:	[Eclipse Project] JDT	Reporter:	Prashant Deva <prashant.deva>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert, Michael_Rennie, stepper
Version:	3.7.1	Keywords:	needinfo
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Prashant Deva

2012-02-24 06:14:48 EST

Build Identifier: 20110916-0149

Changes to a 'run' configuration are not saved *most* of the time.

What these means is, say I add some custom 'vm arguments' in the arguments tab, and press Ok.
When I run the application or go back to the 'run configuration' the arguments have disappeared.

It seems doing the save 2-3 times does eventually result in the arguments being saved, but the count is completely random.

This also applies to the JRE tab when i need to select a different jre to execute the program under.

I am reporting this as major since this is pretty highly reproducible and keeps from launching programs correctly since you dont know if the additional argument you just added was 'actually' added or not, which can lead to a lot of head scratching.

Reproducible: Always

Comment 1 Michael Rennie

2012-02-24 11:12:09 EST

I cannot reproduce this behavior in I20120222-2200 (4.2) using platform provided launch configuration types (Java, Applet, PDE, etc). Prashant, what kind of launch configuration are you editing?

Comment 2 Eike Stepper

2012-11-02 04:17:45 EDT

I'm only experiencing this problem with Chronon Time Traveling debugger being installed and a Chronon tab being shown in the launch config.

Comment 3 Dani Megert

2012-11-02 04:20:32 EDT

(In reply to comment #2)
> I'm only experiencing this problem with Chronon Time Traveling debugger
> being installed and a Chronon tab being shown in the launch config.

Prashant, is this also your scenario?

Comment 4 Michael Rennie

2012-11-02 11:09:29 EDT

(In reply to comment #2)
> I'm only experiencing this problem with Chronon Time Traveling debugger
> being installed and a Chronon tab being shown in the launch config.

Each tab in a launch group has finite control over when (or if) information is written out to the launch configuration. So in this case it would be a problem with the Chronon debugger and not the platform.

I am closing this as worksforme, we can reopen if a test case or steps to reproduce are given.