L$ 2,500 Reward!

Tired of the Client crashing? Want to help us help you? We are offering a L$ 2,500 reward for every reproducible client crash you report to us.

Rules for Eligibility
1. The steps to reproduce the crash must work on more than one computer. (Work with a friend if you only have one computer!)
2. We must be able to reproduce the crash on a machine here at Linden Lab.
3. The steps to reproduce the crash must be written down on a note card and given to Brent Linden. Any objects needed to help the crash must be embedded in the note card.

Chris Linden

Update: Using command line arguments to crash the client will disqualify you from the reward.

Update 2: In the even that multiple people submit a reproducible crash report, the first one to submit steps that we can use to successfully crash the client will receive the reward money.

The successful steps are important, as you don’t necessarily have to be the first person to report a crash, just the first person to gives us detailed instructions that we can use to re-create the crash!

I will be taking over the L$ 2500 reward for reproducible client crash bugs (hereafter known as Bounty Bugs). It would really help me a lot if you follow the following guidelines/suggestions for good, reproducible reports. Remember, you don't get the cash if I can't reproduce your bug on a machine here at Linden!

1. Make sure your drivers are updated. Many crashes are caused by old drivers. Check out this wiki entry for information on how to update your drivers.

2. Please title your notecards with "Bounty Bug:", then a short description of the bug. See the following example which is not a real bug, but could potentially crash the client Bounty Bug: Client crashes when computer is thrown out window

3. Write the steps thoughtfully. "I crash when I upload something" is not a good reprodcible issue. List the steps that you take one by one, such as ...

- Click File > Upload Image ($L10)...
- Choose a .TXT file instead of a .JPG file
- Click the Open button

4. Include your name! I can't really give you the cash if I don't know who you are

5. IM Brent Linden after sending in your notecard to make sure I know you sent it.

Thanks, and good luck!

Bounty Bugs - Get paid for reproducible client crashes!
---
Tired of the Client crashing? Want to help us help you? We are offering a L$ 2,500 reward for every reproducible client crash you report to us.

Rules for Eligibility
---
1. The steps to reproduce the crash must work on more than one computer. (Work with a friend if you only have one computer!)

2. We must be able to reproduce the crash on a machine here at Linden Lab.

3. The steps to reproduce the crash must be written down on a note card and given to Brent Linden. Any objects needed to help the crash must be embedded in the note card.

4. Using command line arguments to crash the client will disqualify you from the reward.

5. In the even that multiple people submit a reproducible crash report, the first one to submit steps that we can use to successfully crash the client will receive the reward money. The successful steps are important, as you don't necessarily have to be the first person to report a crash, just the first person to gives us detailed instructions that we can use to re-create the crash!

6. Malicious scripts (scripts designed to crash the client or the sim, such as prim bombs, nukes, etc) are not eligible for the reward, but you may submit them anyway to be logged as crashers.

Guidelines for Bug Submission
---
It would really help me a lot if you follow the following guidelines/suggestions for good, reproducible reports. Remember, you don't get the cash if I can't reproduce your bug on a machine here at Linden!

1. Make sure your drivers are updated. Many crashes are caused by old drivers. Check out this wiki entry ( http://secondlife.com/tiki/tiki-index.php?page=Finding+the+latest+drivers+for+your+graphics+card ) for information on how to update your drivers.

2. Please title your notecards with "Bounty Bug:", then a short description of the bug. See the following example which is not a real bug, but could potentially crash the client "Bounty Bug: Client crashes when computer is thrown out window"

3. Write the steps thoughtfully. "I crash when I upload something" is not a good reproducible issue. List the steps that you take one by one, such as ...

- Click File > Upload Image ($L10)...
- Choose a .TXT file instead of a .JPG file
- Click the Open button

4. Include your name! I can't really give you the cash if I don't know who you are

5. IM Brent Linden after sending in your notecard to make sure I know you sent it.

Thanks, and good luck!

The following bugs have been reported, along with whether or not we were able to reproduce the bug in the Lab. The most recent bugs I've received are at the top of each category:

Confirmed Crashes
These bugs took my viewer, kicked it a few times and then stood by laughing as it twitched and sobbed. Bugs in this category got the green!

Clicking on a not yet rendered menu selection in a right-click menu crashes viewer: After trying for a while, I got this one to work. It seems to only be an issue if your local FPS is low and causes menu drawing issues. There is no workaround for this one, other than not to right click when your viewer FPS are around 3!

Client crashes when dragging object toward camera set above avatar using llSetCameraEyeOffset: I crashed! To get around this bug, don't drag objects upward toward the camera when looking down on them while sitting on a scripted cube, naturally!

Shadows enabled is crashing client: Everyone and their Aunt Margaret sent this one in (waves to Aunt Margaret)! We were able to reproduce it, and it's on the books. To workaround this one, turn off Shadows in Preferences > Graphics.

Client crashes when moving no-copy objects to inventory and ignoring pop-up: This crashed me, and we're working on it. Until it's fixed, make sure to confirm the pop-up after moving each no-copy object from an object's inventory into your own.

Using "Select Texture" on Linden grass objects causes client crash: Crash, and it's interesting it doesn't happen with trees! We've added it to the list and will be working on it. For now, don't use Select Texture on Linden grass objects!

Uploading image files without an extension causes crash: You guessed it, I crashola'd on this one too. To keep from going poof while uploading, make sure you use the proper extension on any file uploaded to Second Life (.TGA for Targa images, .JPG for JPEG images, .WAV for sound files, .BVH for animation/Poser files).

Typing names in the Muted Residents window causes client crash: Crashed and reported to the developers. For now mute residents by right-clicking them and choosing Mute from the pie menu. You can also mute residents from their profiles.

Unable to Reproduce
These bugs couldn't be reproduced here in the Lab and saw no love from the Governor's piggy bank. Please note that bugs that use LSL to crash the viewer (unless it's a single LSL command that causes the crash, such as llSetText("Boom!",<1,1,1>,1)) are not accepted and will not be listed here.

Parcel media functions can cause a viewer crash when switching from static to live video: Try as I might, I could not duplicate this on my Mac or PC. Again, double-check your drivers before reporting bugs! They are most often at fault with these things.

Pressing ALT and clicking on an avatar causes viewer crash: Not for me, it doesn't! This one turned out to be a bad video driver. Check your video drivers often and make sure you're up-to-date before throwing a Bounty Bug my way!

Bugs from the Crypt
Bugs in this category are old and have been reported before. While these bugs are not eligible for the reward they do still merit being mentioned.

Client crash when sudo-expression is overloaded: Yeah, I had no idea what that meant, either! In layman's terms, you need an expression (other than a comment) that is longer than (are you ready for this?) 16,384 (I wish I could make that blink) characters (or 2^14 for you math majors)! That is one heckuva a string! I'll remind the developers about this one (it's been on the books since 2004), but don't expect a fix soon. For now, use expressions that are just 16,384 characters long, and you won't go /5 boom!

Landmarks in a notecard can cause a crash when trying to copy the landmark to inventory after the notecard is closed: If you click on a landmark in a notecard and do not confirm the copy but instead close the notecard and then confirm the copying of the landmark, you're viewer will go down in flames and throw the Crash Reporter in your face. The workaround here is not to close the notecard the landmark lives in before confirming the copy over.

Updated post with a list of bugs that have been submitted.

Updated post with a list of bugs that have been submitted.

Updated post with a list of bugs that have been submitted.