forked from MiniProfiler/dotnet
-
Notifications
You must be signed in to change notification settings - Fork 0
concurrency problem #1 #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
alexsku
wants to merge
1
commit into
v4
Choose a base branch
from
concurrency-issue-1
base: v4
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,6 +3,8 @@ | |
| using System.Linq; | ||
| using System.Runtime.Serialization; | ||
| using StackExchange.Profiling.Helpers; | ||
| using System.Threading; | ||
| using System.Threading.Tasks; | ||
| #if NET45 | ||
| using System.Web.Script.Serialization; | ||
| #endif | ||
|
|
@@ -22,6 +24,9 @@ public class Timing : IDisposable | |
| private readonly decimal? _minSaveMs; | ||
| private readonly bool _includeChildrenWithMinSave; | ||
|
|
||
| // used for concurrent access detection | ||
| private int _threadsAccessing = 0; | ||
|
|
||
| /// <summary> | ||
| /// Initialises a new instance of the <see cref="Timing"/> class. | ||
| /// Obsolete - used for serialization. | ||
|
|
@@ -253,19 +258,43 @@ public void Stop() | |
| /// </remarks> | ||
| public void AddChild(Timing timing) | ||
| { | ||
| if (Children == null) | ||
| if (Interlocked.Increment(ref _threadsAccessing) > 1) | ||
| throw new Exception("Concurrent access"); | ||
|
|
||
| try | ||
| { | ||
| if (Children == null) | ||
| Children = new List<Timing>(); | ||
|
|
||
| Children.Add(timing); | ||
| if(timing.Profiler == null) | ||
| timing.Profiler = Profiler; | ||
| timing.ParentTiming = this; | ||
| timing.ParentTimingId = Id; | ||
| if (Profiler != null) | ||
| timing.MiniProfilerId = Profiler.Id; | ||
| Children.Add(timing); | ||
| if(timing.Profiler == null) | ||
| timing.Profiler = Profiler; | ||
| timing.ParentTiming = this; | ||
| timing.ParentTimingId = Id; | ||
| if (Profiler != null) | ||
| timing.MiniProfilerId = Profiler.Id; | ||
| } | ||
| finally | ||
| { | ||
| Interlocked.Decrement(ref _threadsAccessing); | ||
| } | ||
| } | ||
|
|
||
| internal void RemoveChild(Timing timing) => Children?.Remove(timing); | ||
| internal void RemoveChild(Timing timing) | ||
| { | ||
| if (Interlocked.Increment(ref _threadsAccessing) > 1) | ||
| throw new Exception("Concurrent access"); | ||
|
|
||
| Task.Delay(10).Wait(); | ||
|
Owner
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. i think this delay is helping to trigger the concurrency since the timing spend much longer doing RemoveChild |
||
| try | ||
| { | ||
| Children?.Remove(timing); | ||
| } | ||
| finally | ||
| { | ||
| Interlocked.Decrement(ref _threadsAccessing); | ||
| } | ||
| } | ||
|
|
||
| /// <summary> | ||
| /// Adds <paramref name="customTiming"/> to this <see cref="Timing"/> step's dictionary of | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if i use profiler.Step for this it would make all foo async timing to be a long tree with each timing having one child only, this is because Timing replaced the head with itself, so creating 1000 timings in parallel would make them all children of each other. My test is a bit more artificial than i would have liked - i explicitly pass the correct head to each timing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also high minSaveMs is important since it triggers the children to be removed from the parent node, if their timing exceeds minSaveMs or minSaveMs is not set they would not be removed and the issue will not get triggered - this is another artificial piece about this test.