search

abaaaay / surveillancesaver

Automatically exported from code.google.com/p/surveillancesaver
0 stars 0 forks source link

Program crashes on exit #16

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Watching screensaver
2.
3.

What is the expected output? What do you see instead?
Just returning to desktop. Instead an error dialog appears asking for
confirmation to send bug report to MS.

What version of the product are you using? On what operating system?
SurveillanceSaver_Alpha_3_Win32.zip.
Windows XP.

Please provide any additional information below.

Original issue reported on code.google.com by ralfe...@gmail.com on 20 May 2008 at 1:30

GoogleCodeExporter commented 8 years ago 
It also crashes with Windows Vista

Original comment by holger.d...@gmail.com on 29 May 2008 at 1:25

GoogleCodeExporter commented 8 years ago 
I am seeing same crash on exit. Running windows XP Pro 
message mo5.surveillance saver has encountered a problem and will have to close.
Running alpha 3

Original comment by pack....@gmail.com on 3 Jul 2008 at 9:30

GoogleCodeExporter commented 8 years ago 
It crashed on exit in Vista but it run no problem

Original comment by yilo...@gmail.com on 14 Nov 2008 at 5:29

GoogleCodeExporter commented 8 years ago 
crashes also on windows xp home

Original comment by suni1...@gmail.com on 23 Dec 2008 at 8:44

GoogleCodeExporter commented 8 years ago 
crashes on exit, also exit from screensaver preview mode.
xp pro sp3

Original comment by goo...@apmicro.co.uk on 18 Jan 2009 at 3:48

GoogleCodeExporter commented 8 years ago 
I've fixed it

when you want to close ScreenSaverFrm, you don't need an event handler for the
FormClosed event that closes its parent; closing the parent 
ScreenSaverManagerFrm
closes the ScreenSaverFrm again, which causes an infinite loop and a stack 
overflow.

Instead, in ScreenSaverFrm.cs you just change the 3 calls to Close() into
Owner.Close() instead; closing the parent will cascade to all the owned windows 
(i.e.
ScreenSaverFrm) automatically. You can then remove the "FormClosed" handler 
entirely.
Job done.

I'd check the fix in myself if I could get subversion to work...

Original comment by goo...@apmicro.co.uk on 18 Jan 2009 at 4:59

Attachments: