You need to log in before you can comment on or make changes to this bug.
This problem can be reproduced on this tutorial: http://www.javapassion.com/handsonlabs/nbprofilerperformance/index.html#Exercise_4 select Perfotmance.processRequest() as root method profile ComputePrimeNumberWebapp application calculate prime number take snapshot This is in log file: *** Profiler engine warning: critical: stack integrity violation on method exit. *** methodId on simulated stack top is unidentifiable *** Profiler engine warning: critical: stack integrity violation on method exit. *** methodId on simulated stack top is unidentifiable *** Profiler engine warning: critical: stack integrity violation on method exit. *** methodId on simulated stack top is unidentifiable *** Profiler engine warning: critical: stack integrity violation on method exit. *** methodId on simulated stack top is unidentifiable
Created an attachment (id=73972) [details] message.log
This stack integrity violation happens when Servlet methods doPost, doGet, etc. are also marked as marker method.
Fixed in profiler-main changeset: 108179:a49a3d7fc5bb tag: tip user: Tomas Hurka <thurka@netbeans.org> date: Fri Nov 21 10:06:04 2008 +0100 summary: bugfix #153578, MarkedCPUCCTNode and ServletRequestCPUCCTNode can be both on the the stack, they both must be removed in methodExit() and methodExitUnstamped()
Integrated into 'main-golden', will be available in build *200811220201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/a49a3d7fc5bb User: Tomas Hurka <thurka@netbeans.org> Log: bugfix #153578, MarkedCPUCCTNode and ServletRequestCPUCCTNode can be both on the the stack, they both must be removed in methodExit() and methodExitUnstamped()
The issue didn't pass the nomination process by nomination cut-off date. It has been marked as 65fixes2-candidate.
Verified in Build 200811240201
The fix was ported into release65_fixes repository. (It is marked as 65fixes1-candidate and it is P2.) http://hg.netbeans.org/release65_fixes/rev/1e1a3b4cedf6
Based on the offline discussion, the issue will be part of 65patch1. The fix has been ported into the release65_fixes repository. http://hg.netbeans.org/release65_fixes/rev/c018e2af226c
