when will the "Assembly is disposed" bug get handled?

I'll tell you: Maybe never.

Why? Because the youtrack exception analyzer picks it up each time it has
been send by Visual Studio and closes it with "duplicate" -- and the
duplicate is a closed bug ticket, too.

So I (and others) can send this day for day for day for day for day and
nothing will ever happen.

--
/\/\arkus.

39 comments

Hello Markus,

Thank you for noticing this! I've reopened that bug (http://youtrack.jetbrains.net/issue/RSRP-213176)
and our devs should handle it. I've also created a bug-report regarding exception
analyzer behavior: http://youtrack.jetbrains.net/issue/RSRP-220952.

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I'll tell you: Maybe never.

Why? Because the youtrack exception analyzer picks it up each time it
has been send by Visual Studio and closes it with "duplicate" -- and
the duplicate is a closed bug ticket, too.

So I (and others) can send this day for day for day for day for day
and nothing will ever happen.



0

Hello Andrew,

Thank you for noticing this! I've reopened that bug (http://youtrack.jetbrains.net/issue/RSRP-213176)
and our devs should handle it. I've also created a bug-report regarding exception
analyzer behavior: http://youtrack.jetbrains.net/issue/RSRP-220952.


Thank you!

BTW: This bug occurs as often as the "Assembly is disposed" bug but did not
get any attention yet -- maybe youtrack should introduce a
duplicate-counter or just vote the original issue on each duplicate:
http://youtrack.jetbrains.net/issue/RSRP-213924#content-tab=1

--
/\/\arkus.

0

Andrew,

and our devs should handle it. I've also created a bug-report regarding exception
analyzer behavior: http://youtrack.jetbrains.net/issue/RSRP-220952.


No one of your devs cares.

I currently can't vote anything different than "broken" or "partially
broken" for the nightly builds because every minute there appears some
exception and reporting them just floods my email account with "resolved +
duplicate" notifications.

For example:
- Assembly has been disposed (while building)
- Add assembly file is called twice (while building)
- The AssemblyFile lifetime has been emergency terminated on its home
thread upon being lost by its owner (while building)

After such errors the entire system is not valid any more: Errors/warnings
start to appear which disappear after restarting VS.

--
/\/\arkus.

0

I currently can't vote anything different than "broken" or "partially


Disabling the voting module is not the solution.

--
/\/\arkus.

0

I totally agree - these are the most problematic bugs, occuring like every time I run VS :(

RSRP-210310 A TryFinally bracket has not been disposed of - marked as fixed, but it is not!

RSRP-214019 Add assembly file is called twice for ... - marked as fixed, but it is not!

RSRP-213176 Assembly is disposed

RSRP-216751 AssemblyFile: The AssemblyFile lifetime has been emergency terminated ...

RSRP-214363 There are some assembly files

0

Hello Markus,

I'm sorry for the delay. The corresponding developer is on a business trip
at the moment and these exceptions should get fixed as soon as he's back.
Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Andrew,

>> and our devs should handle it. I've also created a bug-report
>> regarding exception analyzer behavior:
>> http://youtrack.jetbrains.net/issue/RSRP-220952.
>>

No one of your devs cares.

I currently can't vote anything different than "broken" or "partially
broken" for the nightly builds because every minute there appears some
exception and reporting them just floods my email account with
"resolved + duplicate" notifications.

For example:
- Assembly has been disposed (while building)
- Add assembly file is called twice (while building)
- The AssemblyFile lifetime has been emergency terminated on its home
thread upon being lost by its owner (while building)
After such errors the entire system is not valid any more:
Errors/warnings start to appear which disappear after restarting VS.



0

Hello Markus,

The voting module has been disabled because we've upgraded Confluence, but
now we have enabled it back. Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>> I currently can't vote anything different than "broken" or "partially
>>

Disabling the voting module is not the solution.



0

Hello Martin,

Thank you! I've reopened the bugs you've mentioned.

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I totally agree - these are the most problematic bugs, occuring like
every time I run VS

RSRP-210310 A TryFinally bracket has not been disposed of - *marked as
fixed, but it is not*!
RSRP-214019 Add assembly file is called twice for ... - *marked as
fixed, but it is not*!
RSRP-213176 Assembly is disposed
RSRP-216751 AssemblyFile: The AssemblyFile lifetime has been emergency
terminated ...
RSRP-214363 There are some assembly files
---
Original message URL:
http://devnet.jetbrains.net/message/5297925#5297925



0

Hi,

It seems that I am a "happy" owner of the issue :). It seemed a good idea to me to submit exceptions with actual login into the youtrack. It doesnt look like that any more because for this particular case I have ~ 85 emails notifying me that Exception Analyser merged another dupe into this issue.

FYI I haven't even subscribed for the issue - I just happend to be first one to submit it. Could you please turn this spamming off (at least by reassigning issue to someone else :))?
BTW I have couple of other Exception issues like that one - not as popular though.

Regards,
Sergei

0

Hello Sergei,

Could you please give me the exact issue id? I've looked through the issues
mentioned in this conversation and none of them seem to be reported by you.
Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hi,

It seems that I am a "happy" owner of the issue

. It seemed a good idea to me to submit exceptions with actual login
into the youtrack. It doesnt look like that any more because for this
particular case I have ~ 85 emails notifying me that Exception
Analyser merged another dupe into this issue.

FYI I haven't even subscribed for the issue - I just happend to be
first one to submit it. Could you please turn this spamming off (at
least by reassigning issue to someone else
)?

BTW I have couple of other Exception issues like that one - not as
popular though.

Regards,
Sergei
---
Original message URL:
http://devnet.jetbrains.net/message/5298049#5298049



0

[YouTrack, Updated] Issue RSRP-226401: Assembly is disposed - 90 emails + 100 emails (checked my archived emails)

[YouTrack, Updated] Issue RSRP-209830: tokenBuffer != null - 4 emails


 
Regards,
Sergei

0

Hello Sergei,

I'm afraid the reporter of the issue cannot be changed. However, you can
un-subscribe from such e-mails: open your profile in YouTrack, navigate to
'Fiters and Notifications' tab, find 'Reported by me' search and uncheck
the checkbox on the 'on issue updated' column. Please note that this will
disable all update notifications (but not new comment notifications) for
all issues that you have reported. Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

h1. Issue RSRP-226401: Assembly is disposed - 90
emails + 100 emails (checked my archived emails)

h1. Issue RSRP-209830: tokenBuffer != null - 4
emails

Regards,
Sergei
---
Original message URL:
http://devnet.jetbrains.net/message/5298062#5298062



0

So basicly it is not a good idea to report exceptions with current youtrack login - or you could be spammed.
Maybe its worth considering turning off the signin feature then in resharper exception reporter (at least until youtrack's behaviour changed)?

Regards,
Sergei

0

There is also probably issue with the exception analyzer - these two bugs looks pretty same to me, but the first one was closed some time ago (and reopened now), the second one is still active, both have hundrets of linked duplicates:
http://youtrack.jetbrains.net/issue/RSRP-214019
http://youtrack.jetbrains.net/issue/RSRP-227525

0

Hello Sergei,

It is a good idea to report exceptions with current youtrack login, because
you will be notified when exception is fixed and also because ReSharper developers
can ask you for more information regarding your environment etc. It is a
very rare case actually when one becomes a "happy" owner of an issue that
gets lots of duplicates. We're sorry for the inconvenience!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

So basicly it is not a good idea to report exceptions with current
youtrack login - or you could be spammed.

Maybe its worth considering turning off the signin feature then in
resharper exception reporter (at least until youtrack's behaviour
changed)?

Regards,
Sergei
---
Original message URL:
http://devnet.jetbrains.net/message/5298072#5298072



0

I see 2 flaws in current behaviour:
1. notifications from Exception Analyser never give any interesting info except for merging issues
2. if my issue is not a "happy" == first one - the only notification I would ever receive - is that the issue was merged into another one and closed as a dupe

both cases are useless IMHO.

To correct it I think 2 things could be done:
1. Exception Analyser should never produce any notification.
2. If issue is closed as a dupe - I should be automatically subscribed to the original issue.

0

i have found a similar problem with the excption analyzer. RSRP-233725 to RSRP-233727 which are reported by my today with build 2111 are marked as duplicate of RSRP-199140 which is marked as obsolete Fortunately there is another issue (RSRP-216751) which is open and adresses the same problem.

Regards
Klaus

0

I think if people's R# is still submitting bugs for a particular issue then YouTrack's Exception Analyzer should say "wait a moment, a closed issue can't have new exception reports attached to it. Maybe I should re-open it?" This is why I am going to submit every issue I see from now on as many times as I see it. Maybe this can show how problematic some exception is...

0

This one is still being marked as Fixed (Obsolete) but it is still happening in 2111:

http://youtrack.jetbrains.net/issue/RSRP-195446

0

Is there some way where you can see in YouTrack which issues have the most issues linked to them recently? Maybe this would help to address those issues first.

0

Hello Klaus,

Thank you for this information! RSRP-199140 is closed as Obsolete, but 'Fixed
in build' field is not set, so there's no easy way for Exception Analyzer
to find out that the exception you've submitted comes from a newer build.
I'll see if I can figure out some workaround for this case.

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

i have found a similar problem with the excption analyzer.
http://youtrack.jetbrains.net/issue/RSRP-233725 to
http://youtrack.jetbrains.net/issue/RSRP-233727 which are reported by
my today with build 2111 are marked as duplicate of
http://youtrack.jetbrains.net/issue/RSRP-199140 which is marked as
obsolete Fortunately there is another issue
(http://youtrack.jetbrains.net/issue/RSRP-216751) which is open and
adresses the same problem.

Regards
Klaus
---
Original message URL:
http://devnet.jetbrains.net/message/5298110#5298110



0

Hello Sergei,

Thank you for feedback! We're aware of the problems with current exception
handling and we're planning to address them soon.

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I see 2 flaws in current behaviour:

1. notifications from Exception Analyser never give any interesting
info except for merging issues

2. if my issue is not a "happy" == first one - the only notification I
would ever receive - is that the issue was merged into another one and
closed as a dupe

both cases are useless IMHO.

To correct it I think 2 things could be done:
1. Exception Analyser should never produce any notification.
2. If issue is closed as a dupe - I should be automatically subscribed
to the original issue.
---
Original message URL:
http://devnet.jetbrains.net/message/5298081#5298081



0

I just have to stress this:

After such errors the entire system is not valid any more: Errors/warnings
start to appear which disappear after restarting VS.


After 1 single "assembly is disposed" exception the entire R#-meta-model is
broken and I get errors like:

  • 'UsedImplicitly' is not an attribute

  • Catch target must derive from Exception (on "catch (Exception ex) {}" !!)

and 1001 more

--
/\/\arkus.

0

I am still seeing these in 2116

0

Hello All,

Presumably we have fixed this problem, so please try the next build. Let
me know if this helps. Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I am still seeing these in 2116

---
Original message URL:
http://devnet.jetbrains.net/message/5298700#5298700



0

Andrew,

Presumably we have fixed this problem, so please try the next build. Let
me know if this helps. Thank you!


Assembly is disposed? No:
http://youtrack.jetbrains.net/issue/RSRP-240087

--
/\/\arkus.

0

Same here.. got it three times now.

YouTrack entries have been created.

Kind regards,
Henning

"Markus Springweiler"  wrote in message news:fk5snzxoch3x.dlg@sihv.de...

Andrew,

Presumably we have fixed this problem, so please try the next build. Let
me know if this helps. Thank you!


Assembly is disposed? No:
http://youtrack.jetbrains.net/issue/RSRP-240087

--
/\/\arkus.

0

Issues

RSRP-240112
RSRP-240113
RSRP-240114

"Henning Krause"  wrote in message
news:imuo0l$jrv$1@nntp-server.labs.intellij.net...

Same here.. got it three times now.

YouTrack entries have been created.

Kind regards,
Henning

"Markus Springweiler"  wrote in message news:fk5snzxoch3x.dlg@sihv.de...

Andrew,

Presumably we have fixed this problem, so please try the next build. Let
me know if this helps. Thank you!


Assembly is disposed? No:
http://youtrack.jetbrains.net/issue/RSRP-240087

--
/\/\arkus.

0

Hello Markus,

Thank you for the info! We'll keep investigating this problem.

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Andrew,

>> Presumably we have fixed this problem, so please try the next build.
>> Let me know if this helps. Thank you!
>>

Assembly is disposed? No:
http://youtrack.jetbrains.net/issue/RSRP-240087



0

i still got Exceptions which are marked as duplicate of RSRP-199140 (using build 2117 now). The following exceptions occurs always when i build or rebuild my solution:

RSRP-240389
RSRP-240390
RSRP-240391
RSRP-240392

I'm afraid they are not recognized by you because i have them since several builds (don't remember when it starts).

I also noticed that the Windows Forms Designer had problems to open a Form after these exceptions occured. Today it happened that i rebuild my soloution with not editor window open. In this case the exceptions didn't occur. Also the Forms Designer could open the above mentioned form without problems (i didn't made any changes on the form's code)

All happened in VS 2008 while working on a VB solution.

Regards
Klaus

0

Please sign in to leave a comment.