Activity overview
Latest activity by SamNabialek
HI, Jessica, Not at this point. I have other higher priorities at the moment. As we're planning to buy licences anyway, I'm sure we'll be able to revisit the issue at some point in the near future. Thanks for your help anyway,
/ comments
HI, Jessica,Not at this point. I have other higher priorities at the moment. As we're planning to buy licences anyway, I'm sure we'll be able to revisit the issue at some point in the near future.T...
Hi, Jessica, Unfortunately, not. The application, the COM object and the data required to run the application against are considered sensitive. Plus my trial period has now expired.
/ comments
Hi, Jessica,Unfortunately, not. The application, the COM object and the data required to run the application against are considered sensitive. Plus my trial period has now expired.
I was mistaken! Even after a reboot it makes no difference. Our software uses a COM object to display progress information. I can take a snapshot at any point until that COM connection is created. Once that inter-process connection is in place, any attempt at a snapshot kills the process that sends the messages (the process being profiled). Ideally, I'd like to remove the COM object and log messages in a different manner, but that isn't likely to be sanctioned any time soon.
/ comments
I was mistaken! Even after a reboot it makes no difference. Our software uses a COM object to display progress information. I can take a snapshot at any point until that COM connection is created. ...
HI, Jessica, The issue remains until I switch to the attach mode of operation. It did require me to make the process sleep for 60 seconds so I could attach to the process in time to take the first important snapshot. Other than that, it seems to be working fine. Does that help in fixing the issue when started from within the Memeory Profiler? So, to answer your questions, Yes, Yes, Yes, No.
:-)
===Update=== It only worked the first time. After that every subsequent attempt to attach to a process crashes the program being profiled about 2 seconds after the memory snapshot is initiated. Could it be related that the fact that the program is sleeping at this point? There's a 10 second Thread.Sleep() so I have time to take a valid snapshot under known conditions. I tried using a Console.Read() for the same purpose but I get the same failure. I'll try a reboot.
/ comments
HI, Jessica,The issue remains until I switch to the attach mode of operation. It did require me to make the process sleep for 60 seconds so I could attach to the process in time to take the first ...
Hi, Jessica, First Error is:
Application: Sandbox.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFD8263B1AD (00007FFD82040000) with exit code 80131506. Second is:
Faulting application name: Sandbox.exe, version: 1.0.0.8255, time stamp: 0x5f0ffae7 Faulting module name: clr.dll, version: 4.8.4180.0, time stamp: 0x5e7d21b3 Exception code: 0xc0000005 Fault offset: 0x00000000005fb1ad Faulting process id: 0x1560c Faulting application start time: 0x01d65b3eba549617 Faulting application path: T:\SRC\Core\Compiler\CompilerGUI\1.0.0\Bin\Sandbox.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: a3c86782-f82a-4bbb-bf99-9bb86c73214a Faulting package full name: Faulting package-relative application ID:
Subsequent Information is:
Fault bucket 1904641844225617697, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Sandbox.exe P2: 1.0.0.8255 P3: 5f0ffae7 P4: clr.dll P5: 4.8.4180.0 P6: 5e7d21b3 P7: c0000005 P8: 00000000005fb1ad P9: P10: Help any? / comments
Hi, Jessica,First Error is:
Application: Sandbox.exeFramework Version: v4.0.30319Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFD8263B1AD (00007F...
Why does taking a snapshot kill the process being profiled?
The process was built using VS 2019 and Postsharp 6.6.10. It targets .NET 4.0 running under Win 10 Enterprise.I click on take a snapshot and get a pop-up telling me that the process has stopped wor...
When I try to take a snapshot of my running process. It dies.
The process was built using VS 2019 and Postsharp 6.6.10. It targets .NET 4.0 running under Win 10 Enterprise.Any idea why I cannot profile what is a simple process? I took out the GUI and had the ...