Operation Id is changeable when trace WPF operations by embedded ETW provider












1














I'm trying to trace WPF operations by ETW provider embedded into PresentationSource.
When I traced real application I was bit by changing already triggered operation Id from Post to Start phase.



At the source code I found that Id is relied on address of the object which might be changed during GC operation:
https://referencesource.microsoft.com/#windowsbase/Base/System/Windows/Threading/DispatcherOperation.cs,dff34e59b0cffd1e



Does anybody know how to track by ETW such object relocation?










share|improve this question





























    1














    I'm trying to trace WPF operations by ETW provider embedded into PresentationSource.
    When I traced real application I was bit by changing already triggered operation Id from Post to Start phase.



    At the source code I found that Id is relied on address of the object which might be changed during GC operation:
    https://referencesource.microsoft.com/#windowsbase/Base/System/Windows/Threading/DispatcherOperation.cs,dff34e59b0cffd1e



    Does anybody know how to track by ETW such object relocation?










    share|improve this question



























      1












      1








      1







      I'm trying to trace WPF operations by ETW provider embedded into PresentationSource.
      When I traced real application I was bit by changing already triggered operation Id from Post to Start phase.



      At the source code I found that Id is relied on address of the object which might be changed during GC operation:
      https://referencesource.microsoft.com/#windowsbase/Base/System/Windows/Threading/DispatcherOperation.cs,dff34e59b0cffd1e



      Does anybody know how to track by ETW such object relocation?










      share|improve this question















      I'm trying to trace WPF operations by ETW provider embedded into PresentationSource.
      When I traced real application I was bit by changing already triggered operation Id from Post to Start phase.



      At the source code I found that Id is relied on address of the object which might be changed during GC operation:
      https://referencesource.microsoft.com/#windowsbase/Base/System/Windows/Threading/DispatcherOperation.cs,dff34e59b0cffd1e



      Does anybody know how to track by ETW such object relocation?







      c# wpf garbage-collection dispatcher etw






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 20 '18 at 16:20







      Evgeny Burmakov

















      asked Nov 20 '18 at 14:06









      Evgeny BurmakovEvgeny Burmakov

      185




      185
























          1 Answer
          1






          active

          oldest

          votes


















          1














          Such movement might be tracked by:



          ProviderName: "Microsoft-Windows-DotNETRuntime"

          EventName: "GC/GCBulkMovedObjectRanges"

          Event might be parsed by ClrTraceEventParser.GCBulkMovedObjectRanges



          Originally answered there:



          https://social.msdn.microsoft.com/Forums/en-US/7b6f9918-60ee-4e23-b443-42b4895775ad/how-to-track-change-of-wpf-dispatcheroperation-id?forum=netfxbcl



          UPDATE:



          Due to tracing WPF operations I would say that approach with changeable ID is worst ever implementation. It is implemented incorrectly.



          Id has fixed address position during gather that Id but whole operation isn't ensure that tracing message contains correct address. It might be already moved when event is raised.



          I got next event sequence:

          - WClientUIContextPost

          - GCBulkMovedObjectRanges

          - WClientUIContextPost



          Where last one may contains moved or unmoved Id. Only gods know.



          The event GCBulkMovedObjectRanges is usable in 95%. But sometimes it is fails.



          So it no way to track it reliable. Very sadly that this architectural/implementation mistake turn feature unusable.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53394807%2foperation-id-is-changeable-when-trace-wpf-operations-by-embedded-etw-provider%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            Such movement might be tracked by:



            ProviderName: "Microsoft-Windows-DotNETRuntime"

            EventName: "GC/GCBulkMovedObjectRanges"

            Event might be parsed by ClrTraceEventParser.GCBulkMovedObjectRanges



            Originally answered there:



            https://social.msdn.microsoft.com/Forums/en-US/7b6f9918-60ee-4e23-b443-42b4895775ad/how-to-track-change-of-wpf-dispatcheroperation-id?forum=netfxbcl



            UPDATE:



            Due to tracing WPF operations I would say that approach with changeable ID is worst ever implementation. It is implemented incorrectly.



            Id has fixed address position during gather that Id but whole operation isn't ensure that tracing message contains correct address. It might be already moved when event is raised.



            I got next event sequence:

            - WClientUIContextPost

            - GCBulkMovedObjectRanges

            - WClientUIContextPost



            Where last one may contains moved or unmoved Id. Only gods know.



            The event GCBulkMovedObjectRanges is usable in 95%. But sometimes it is fails.



            So it no way to track it reliable. Very sadly that this architectural/implementation mistake turn feature unusable.






            share|improve this answer




























              1














              Such movement might be tracked by:



              ProviderName: "Microsoft-Windows-DotNETRuntime"

              EventName: "GC/GCBulkMovedObjectRanges"

              Event might be parsed by ClrTraceEventParser.GCBulkMovedObjectRanges



              Originally answered there:



              https://social.msdn.microsoft.com/Forums/en-US/7b6f9918-60ee-4e23-b443-42b4895775ad/how-to-track-change-of-wpf-dispatcheroperation-id?forum=netfxbcl



              UPDATE:



              Due to tracing WPF operations I would say that approach with changeable ID is worst ever implementation. It is implemented incorrectly.



              Id has fixed address position during gather that Id but whole operation isn't ensure that tracing message contains correct address. It might be already moved when event is raised.



              I got next event sequence:

              - WClientUIContextPost

              - GCBulkMovedObjectRanges

              - WClientUIContextPost



              Where last one may contains moved or unmoved Id. Only gods know.



              The event GCBulkMovedObjectRanges is usable in 95%. But sometimes it is fails.



              So it no way to track it reliable. Very sadly that this architectural/implementation mistake turn feature unusable.






              share|improve this answer


























                1












                1








                1






                Such movement might be tracked by:



                ProviderName: "Microsoft-Windows-DotNETRuntime"

                EventName: "GC/GCBulkMovedObjectRanges"

                Event might be parsed by ClrTraceEventParser.GCBulkMovedObjectRanges



                Originally answered there:



                https://social.msdn.microsoft.com/Forums/en-US/7b6f9918-60ee-4e23-b443-42b4895775ad/how-to-track-change-of-wpf-dispatcheroperation-id?forum=netfxbcl



                UPDATE:



                Due to tracing WPF operations I would say that approach with changeable ID is worst ever implementation. It is implemented incorrectly.



                Id has fixed address position during gather that Id but whole operation isn't ensure that tracing message contains correct address. It might be already moved when event is raised.



                I got next event sequence:

                - WClientUIContextPost

                - GCBulkMovedObjectRanges

                - WClientUIContextPost



                Where last one may contains moved or unmoved Id. Only gods know.



                The event GCBulkMovedObjectRanges is usable in 95%. But sometimes it is fails.



                So it no way to track it reliable. Very sadly that this architectural/implementation mistake turn feature unusable.






                share|improve this answer














                Such movement might be tracked by:



                ProviderName: "Microsoft-Windows-DotNETRuntime"

                EventName: "GC/GCBulkMovedObjectRanges"

                Event might be parsed by ClrTraceEventParser.GCBulkMovedObjectRanges



                Originally answered there:



                https://social.msdn.microsoft.com/Forums/en-US/7b6f9918-60ee-4e23-b443-42b4895775ad/how-to-track-change-of-wpf-dispatcheroperation-id?forum=netfxbcl



                UPDATE:



                Due to tracing WPF operations I would say that approach with changeable ID is worst ever implementation. It is implemented incorrectly.



                Id has fixed address position during gather that Id but whole operation isn't ensure that tracing message contains correct address. It might be already moved when event is raised.



                I got next event sequence:

                - WClientUIContextPost

                - GCBulkMovedObjectRanges

                - WClientUIContextPost



                Where last one may contains moved or unmoved Id. Only gods know.



                The event GCBulkMovedObjectRanges is usable in 95%. But sometimes it is fails.



                So it no way to track it reliable. Very sadly that this architectural/implementation mistake turn feature unusable.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 29 '18 at 10:07

























                answered Nov 22 '18 at 14:52









                Evgeny BurmakovEvgeny Burmakov

                185




                185






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53394807%2foperation-id-is-changeable-when-trace-wpf-operations-by-embedded-etw-provider%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Paul Cézanne

                    UIScrollView CustomStickyHeader Resize height generates problems when scroll is too fast

                    Angular material date-picker (MatDatepicker) auto completes the date on focus out