[X] My Assistant

[papuccino1]

Hey there. I thought it would be fun if you guys shared code that "broke" your PC. For instance a stack overflow, etc.

This particular glitch in my code was found in approx. 6 seconds but was 100% new to me to be exact. Quite exciting stuff.

Use this in a part of your code.

csharp

for (int i = 0; i <= 9; i++)
                    {
                        int x = Randomer.Next(1, 8);
                        System.Threading.Thread.Sleep(20);
                        if (!(GeneratedNumbers.Contains(x)))
                        {
                            GeneratedNumbers[i] = x;
                        }
                        else
                            i--;                        
                    }

This little algorithm was made there were no repeated random numbers in my int array. Try to find out what's wrong with it. xD

Lesson learned I say, because neither the compiler nor Windows itself threw any sort of error. The program just froze there in space and time, looking (fruitlessly) for a number that isn't repeated.

Share some more!

[masteryee]

While it's possible for your loop to become infinite prior to i = 8, your loop definitely becomes an infinite loop around i = 8 because all 8 numbers are already in your array, so your loop ends up infinitely performing an i-- for every i++, so your iteration index never moves on.

Here's a random glitch off the top of my head. Assuming I have a simple form with a TextBox and Button and nothing more, why does the following freeze your program:

C#

private void button_Click(object sender, EventArgs e)
{
     Invoke(new Action(() => textBox.Text = "You've won a million dollars!"));
}

The Visual Studio debugger may actually tell you the answer, lol. If it does, then tell me the theory behind why it freezes the program.

[masteryee]

Oops, I finally tested my code and it did not cause a deadlock like I thought it would. What the hell's the point of InvokeRequired then if you can call Invoke from any thread? Sorry everyone.

[AdamSpeight2008]

A one line program that is hard to kill.
Warning!! Requires a restart to stop.

CODE

Module KillMeIfYouCan
Sub Main()
  Process.Start(System.Windows.Forms.Application.ExecutablePath)
End Sub
End Module

[jacobjordan]

A one line program that is hard to kill.
Warning!! Requires a restart to stop.

CODE

Module KillMeIfYouCan
Sub Main()
  Process.Start(System.Windows.Forms.Application.ExecutablePath)
End Sub
End Module

I prefer this

csharp

        static void Main(string[] args)
        {
            while (true)
            {
                System.Diagnostics.Process.Start(System.Windows.Forms.Application.ExecutablePath);
            }
        }

[Locke]

Alright, AdamSpeight2008 and jacobjordan...you stumped me. I'm too lazy to Google it (), so what does the System.Diagnostics.Process.Start(System.Windows.Forms.Application.ExecutablePath); do?

This post has been edited by Locke: 4 Jul, 2009 - 07:07 PM

[AdamSpeight2008]

System.Diagnostics.Process.Start()Starts a new process.
System.Windows.Forms.Application.ExecutablePath The location of the exe of this program.
In my case it starts a new instance of the program and runs it, in jacobjordan it creates a multiple instances (Exponential growth)

[Locke]

That's what I figured, since it had to keep the computer occupied and running itself silly somehow.

Yay for useless (if only for fun ) process calls!

This post has been edited by Locke: 5 Jul, 2009 - 10:04 AM

[firexware]

CODE

    Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
        Application.DoEvents() 'let it show the window
        Application.Restart()
    End Sub

i find that more annoying then starting hundreds of forms

[RudiVisser]

One of our services has 2 components that monitor each other, so if one goes down, the other would restart it instantly, and vice versa.

A big problem arose when I changed the .exe name and it constantly thought it was not started

[doucet.damon]

A funny little thing I made for a friend was to create 4 forms, where each one had the size of 1/2 the width of the screen by 1/2 the height of the screen. In the Main method, drop the Application.Run() call and replace it with just initializing and showing the 4 forms; position one in each corner of the screen. Turn the "Show In Taskbar" property to false, the "Top Most" to true, and override the CreateParams property on the form so that it doesn't show in Alt Tab (just to be nice looking). In Main() do a while(true) to loop through changing the background colors of the forms to something different (incrementing each's value in a predefined array), so it flashes like crazy, and the only way you can get out of it (without restarting) is if your Task Manager has "Always on Top" checked.

[Donnie1581]

A funny little thing I made for a friend was to create 4 forms, where each one had the size of 1/2 the width of the screen by 1/2 the height of the screen. In the Main method, drop the Application.Run() call and replace it with just initializing and showing the 4 forms; position one in each corner of the screen. Turn the "Show In Taskbar" property to false, the "Top Most" to true, and override the CreateParams property on the form so that it doesn't show in Alt Tab (just to be nice looking). In Main() do a while(true) to loop through changing the background colors of the forms to something different (incrementing each's value in a predefined array), so it flashes like crazy, and the only way you can get out of it (without restarting) is if your Task Manager has "Always on Top" checked.

Awesome, I'm going to screw with some people using this!