FIX: You experience a System.IndexOutOfRangeException error or a System.NullReferenceException error when you use the Queue object in the .NET Framework 1.1 (843072)



The information in this article applies to:

  • Microsoft .NET Framework 1.1

SYMPTOMS

You may experience one or more of the following problems:
  • Problem 1
    You call the TrimToSize method, and then you call the Dequeue method. If you call the Enqueue method later, you may experience a System.IndexOutOfRangeException error. When this problem occurs, you receive an error message that is similar to the following:
    Index was outside the bounds of the array
  • Problem 2
    When you call the Clone method, the Count property of the resulting clone reports correctly that it contains the same number of queued items as the original. However, when you call the Dequeue method to remove items from the Queue object, you may experience a System.NullReferenceException error. When this problem occurs, you receive an error message that is similar to the following:
    Object reference not set to an instance of an object

CAUSE

These problems occur because a bug exists in the .NET Framework 1.1.

RESOLUTION

This software update corrects these two problems that affect the System.Collections.Queue class in the Microsoft .NET Framework version 1.1.

Software update information

A supported software update is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This software update may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft .NET Framework 1.1 service pack that contains this software update.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the software update. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have the .NET Framework 1.1 installed to apply this software update.

Restart requirement

On the Microsoft Windows Server 2003 operating system, you may have to restart your computer after you apply this software update. On other operating systems, you may have to restart your computer, depending on the applications that are running when you apply this software update.

Software update replacement information

This software update does not replace any other software updates.

File information

The English version of this software update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version        Size       File name
   ---------------------------------------------------------------
   27-May-2004  20:02  1.1.4322.1048     77,824  Corperfmonext.dll
   27-May-2004  19:59  1.1.4322.1048    282,624  Fusion.dll
   27-May-2004  19:59  1.1.4322.1048    311,296  Mscorjit.dll
   27-May-2004  20:02  1.1.4322.1048    102,400  Mscorld.dll
   28-May-2004  14:37  1.1.4322.1048  2,093,056  Mscorlib.dll
   27-May-2004  19:52                    10,760  Mscorlib.ldo
   27-May-2004  20:00  1.1.4322.1048  2,502,656  Mscorsvr.dll
   27-May-2004  20:01  1.1.4322.1048  2,494,464  Mscorwks.dll

WORKAROUND

To work around these problems, use one of the following methods, depending on the problem that you are experiencing:
  • Problem 1 only
    Call the TrimToSize method again after you call the Dequeue method. If you do this, later calls to the Enqueue method will work correctly.
  • Problem 1 and problem 2
    Create a new queue that is based on the old queue. For example, use the following structure:
    q2 = new Queue(q1)
    You will not experience these problems when you use the new queue instead of the old queue.
The suitability of these workarounds depends on your application's requirements. These workarounds work well if you are using Queue objects that contain few items, and you are not using the Queue objects in multiple parts of your application. However, if your Queue objects contain many items, these workarounds may significantly affect your application's performance.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates


Modification Type:MajorLast Reviewed:4/7/2006
Keywords:kbQFE KBHotfixServer kbBug kbfix kbNetFrame110preSP1fix KB843072 kbAudDeveloper