Can not restart application. Use CR_INST_APP_RESTART flag

[GoogleCodeExporter]

***NOTE*** Please do create a NEW issue per each detected bug! Do not list
all detected problems in single issue record!

What steps will reproduce the problem?
1.Install Crashrpt and set dwFlags |= CR_INST_APP_RESTART
2.When crash occurs, the application can not restart.
3.

What is the expected output? What do you see instead?

What version of CrashRpt are you using?

What is your version of Visual Studio?

What is your version of Windows operating system?

Please provide any additional information below.

Original issue reported on code.google.com by sloagni...@gmail.com on 21 Sep 2012 at 9:25

[GoogleCodeExporter]

I tried to reproduce the issue but the app restart feature worked as expected.

What I did (with WTLDemo app):
1. Install Crashrpt and set dwFlags |= CR_INST_APP_RESTART
2. Run the app and wait for one minute
3. Crash the app
4. When crash occurs, the report window is displayed
5. Click "Close the program" button and the application restarts.

Probably, you did not wait for a minute. As the documentation states, "The 
application is restarted only if at least 60 seconds have elapsed since its 
start up. This is done to avoid cyclic restarts of an application that crashes 
right on its start up. Also, the application is restarted only if the user does 
provide his/her consent." 
http://crashrpt.sourceforge.net/docs/html/misc_api_features.html

Does this resolve your issue?

Original comment by zexspect...@gmail.com on 22 Sep 2012 at 1:59

• Changed state: Reviewed

[GoogleCodeExporter]

Issue 166 has been merged into this issue.

Original comment by zexspect...@gmail.com on 22 Sep 2012 at 2:06

[GoogleCodeExporter]

This issue was closed by revision r1422.

Original comment by zexspect...@gmail.com on 9 Oct 2012 at 4:14

• Changed state: Fixed

[GoogleCodeExporter]

"The application is restarted only if at least 60 seconds have elapsed since 
its start up. This is done to avoid cyclic restarts of an application that 
crashes right on its start up. Also, the application is restarted only if the 
user does provide his/her consent." 

I understand the caution to avoid cyclic restarts. But such policy may break 
the consistence. It would be good that 60 second is exposed as an option in 
CR_INSTALL_INFO and allow users to overwrite at their own risks. 

Thanks.

Original comment by zxpat...@gmail.com on 30 Aug 2013 at 12:57

[GoogleCodeExporter]

Original comment by zexspect...@gmail.com on 31 Aug 2013 at 3:26

• Changed state: Accepted

[GoogleCodeExporter]

You can now override the default restart timeout (in seconds) 
using the CR_INSTALL_INFO::nRestartTimeout structure field.

Original comment by zexspect...@gmail.com on 13 Oct 2013 at 2:20

[GoogleCodeExporter]

This issue was closed by revision r1638.

Original comment by zexspect...@gmail.com on 13 Oct 2013 at 2:20

• Changed state: Fixed