Out of Memory Errors - Fixed?

Over the past months and through many versions of ReSharper, we have
experienced random out of memory errors in Visual Studio which require
shutting down and restarting the application. This has been time consuming
and frustrating - especially given the amount of time it takes to reload and
get ReSharper ready to go.

Yesterday, I obtained this patch from Microsoft which seems to have fixed
the problem.

http://support.microsoft.com/kb/894472/en-us

Only time will tell if this is a permanent fix.

Right now you must submit an incident to the the patch - Maybe our friends
at JetBrains could slipstream this into their installer if it really solves
the problem.

Jeff


4 comments
Comment actions Permalink

Hello Jeff,

We detected several memory leaks in ReSharper 2.0 and 2.0.1. We plan to fix
them in 2.0.2.

Over the past months and through many versions of ReSharper, we have
experienced random out of memory errors in Visual Studio which require
shutting down and restarting the application. This has been time
consuming and frustrating - especially given the amount of time it
takes to reload and get ReSharper ready to go.

Yesterday, I obtained this patch from Microsoft which seems to have
fixed the problem.

http://support.microsoft.com/kb/894472/en-us

Only time will tell if this is a permanent fix.

Right now you must submit an incident to the the patch - Maybe our
friends at JetBrains could slipstream this into their installer if it
really solves the problem.

Jeff

Best regards,
Andrey Simanovsky


0
Comment actions Permalink

Fixing the leaks is a good thing.

However, we saw many cases where task manager reported plenty of memory
available yet Visual Studio said out of memory.

"Andrey Simanovsky (JetBrains)" <ands@intellij.com> wrote in message
news:c8a8a15d134f98c8a1876630dc77@news.intellij.net...

Hello Jeff,

>

We detected several memory leaks in ReSharper 2.0 and 2.0.1. We plan to
fix them in 2.0.2.

>
>> Over the past months and through many versions of ReSharper, we have
>> experienced random out of memory errors in Visual Studio which require
>> shutting down and restarting the application. This has been time
>> consuming and frustrating - especially given the amount of time it
>> takes to reload and get ReSharper ready to go.
>>
>> Yesterday, I obtained this patch from Microsoft which seems to have
>> fixed the problem.
>>
>> http://support.microsoft.com/kb/894472/en-us
>>
>> Only time will tell if this is a permanent fix.
>>
>> Right now you must submit an incident to the the patch - Maybe our
>> friends at JetBrains could slipstream this into their installer if it
>> really solves the problem.
>>
>> Jeff
>>

Best regards,
Andrey Simanovsky

>



0
Comment actions Permalink

I thought I would just let everyone know... I installed the mentioned
hotfix several days ago but experience regular "Out of Memory" errors.

It is really frustrating that this bug has still not been fixed; there
seem to be a good number of people who experience this problem regularly.

- Nate


Jeff wrote:

Fixing the leaks is a good thing.

However, we saw many cases where task manager reported plenty of memory
available yet Visual Studio said out of memory.

"Andrey Simanovsky (JetBrains)" <ands@intellij.com> wrote in message
news:c8a8a15d134f98c8a1876630dc77@news.intellij.net...

>> Hello Jeff,
>>
>> We detected several memory leaks in ReSharper 2.0 and 2.0.1. We plan to
>> fix them in 2.0.2.
>>
>>> Over the past months and through many versions of ReSharper, we have
>>> experienced random out of memory errors in Visual Studio which require
>>> shutting down and restarting the application. This has been time
>>> consuming and frustrating - especially given the amount of time it
>>> takes to reload and get ReSharper ready to go.
>>>
>>> Yesterday, I obtained this patch from Microsoft which seems to have
>>> fixed the problem.
>>>
>>> http://support.microsoft.com/kb/894472/en-us
>>>
>>> Only time will tell if this is a permanent fix.
>>>
>>> Right now you must submit an incident to the the patch - Maybe our
>>> friends at JetBrains could slipstream this into their installer if it
>>> really solves the problem.
>>>
>>> Jeff
>>>
>> Best regards,
>> Andrey Simanovsky
>>
>>


0
Comment actions Permalink

Nate,
Now that we've had some time to run using this patch, I can say the results
have been mixed. I rarely experience the problem but my colleague still has
it.
Jeff

"Nate Zobrist" <zobie@zobie.com> wrote in message
news:eef66o$4p5$1@is.intellij.net...
>I thought I would just let everyone know... I installed the mentioned
>hotfix several days ago but experience regular "Out of Memory" errors.
>

It is really frustrating that this bug has still not been fixed; there
seem to be a good number of people who experience this problem regularly.

>

- Nate

>
>

Jeff wrote:

>> Fixing the leaks is a good thing.
>>
>> However, we saw many cases where task manager reported plenty of memory
>> available yet Visual Studio said out of memory.
>>
>> "Andrey Simanovsky (JetBrains)" <ands@intellij.com> wrote in message
>> news:c8a8a15d134f98c8a1876630dc77@news.intellij.net...
>>> Hello Jeff,
>>>
>>> We detected several memory leaks in ReSharper 2.0 and 2.0.1. We plan to
>>> fix them in 2.0.2.
>>>
>>>> Over the past months and through many versions of ReSharper, we have
>>>> experienced random out of memory errors in Visual Studio which require
>>>> shutting down and restarting the application. This has been time
>>>> consuming and frustrating - especially given the amount of time it
>>>> takes to reload and get ReSharper ready to go.
>>>>
>>>> Yesterday, I obtained this patch from Microsoft which seems to have
>>>> fixed the problem.
>>>>
>>>> http://support.microsoft.com/kb/894472/en-us
>>>>
>>>> Only time will tell if this is a permanent fix.
>>>>
>>>> Right now you must submit an incident to the the patch - Maybe our
>>>> friends at JetBrains could slipstream this into their installer if it
>>>> really solves the problem.
>>>>
>>>> Jeff
>>>>
>>> Best regards,
>>> Andrey Simanovsky
>>>
>>>
>>

0

Please sign in to leave a comment.