Online Forums
Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.
Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.
Do not use the Contact page for technical issues.
QuickOPC with PowerShell - Register-ObjectEvent
16 Jan 2018 06:49 - 16 Jan 2018 06:50 #5870
by support
Replied by support on topic QuickOPC with PowerShell - Register-ObjectEvent
Hello, I investigated this quite a lot, but unfortunately I have no good result so far.
Here is what I have found: It appears that most memory is occupied by the event arguments objects that we send to PowerShell. But it is not us holding - it is some kind of queue inside PowerShell that is not being cleared. Attached are screenshots from memory analysis from one of the test runs that show that the "root" that is holding all the objects is a local variable in PowerShell:
But when I made small programs that mimic what we do, PowerShell did not show signs of the leak. I could not think of something special we do, except for a library that we use and that takes over some system calls. After turning it off (see kb.opclabs.com/How_to_disable_prerequisites_boxing, done in the configuration file powershell_ise.exe.config), it seemed that the memory leak indeed disappeared. But after roughly 30 minutes, the memory started growing again.
I suggest that you try the steps at kb.opclabs.com/How_to_disable_prerequisites_boxing as well, if for nothing then for a possibility that the boxing can also have something to do with the crashes (which I could not reproduce at all).
But, if the memory leak persists, I would recommend you to use the "event pull" mechanism instead (as you already suggested). The problem seem to be related to PowerShell event processing only, so this resolve it.
Here is what I have found: It appears that most memory is occupied by the event arguments objects that we send to PowerShell. But it is not us holding - it is some kind of queue inside PowerShell that is not being cleared. Attached are screenshots from memory analysis from one of the test runs that show that the "root" that is holding all the objects is a local variable in PowerShell:
But when I made small programs that mimic what we do, PowerShell did not show signs of the leak. I could not think of something special we do, except for a library that we use and that takes over some system calls. After turning it off (see kb.opclabs.com/How_to_disable_prerequisites_boxing, done in the configuration file powershell_ise.exe.config), it seemed that the memory leak indeed disappeared. But after roughly 30 minutes, the memory started growing again.
I suggest that you try the steps at kb.opclabs.com/How_to_disable_prerequisites_boxing as well, if for nothing then for a possibility that the boxing can also have something to do with the crashes (which I could not reproduce at all).
But, if the memory leak persists, I would recommend you to use the "event pull" mechanism instead (as you already suggested). The problem seem to be related to PowerShell event processing only, so this resolve it.
Please Log in or Create an account to join the conversation.
03 Jan 2018 12:46 #5794
by Enrico
Replied by Enrico on topic QuickOPC with PowerShell - Register-ObjectEvent
Hi again,
here are the results from the debugging with Visual Studio.
(1) The first picture shows the exception leading to the powershell crash. The full error code is this:
Ausnahmefehler bei 0x000007FEFD27A06D (KernelBase.dll) in PowerShellToolsProcessHost.exe: 0xE0434352 (Parameter: 0xFFFFFFFF80131501, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x000007FEE7430000)
(2) The second picture shows the windows heap. It starts increasing slowly and all of a sudden it gets crazzy. I have highligted the last heap snapshot. That indicates the service/process filling up the heap.
By the way, when I activate the heap monitoring, the script runs more stable. It fails when there is a memory overrun. Thus the heap monitroing does something that keeps everything in line.
(3) the third picture shows the windows heap when putting the powershell into the sleep mode. The same behaviour. By the may the memory allocation is in the range of 5 GB (and increasing
)
here are the results from the debugging with Visual Studio.
(1) The first picture shows the exception leading to the powershell crash. The full error code is this:
Ausnahmefehler bei 0x000007FEFD27A06D (KernelBase.dll) in PowerShellToolsProcessHost.exe: 0xE0434352 (Parameter: 0xFFFFFFFF80131501, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x000007FEE7430000)
(2) The second picture shows the windows heap. It starts increasing slowly and all of a sudden it gets crazzy. I have highligted the last heap snapshot. That indicates the service/process filling up the heap.
By the way, when I activate the heap monitoring, the script runs more stable. It fails when there is a memory overrun. Thus the heap monitroing does something that keeps everything in line.
(3) the third picture shows the windows heap when putting the powershell into the sleep mode. The same behaviour. By the may the memory allocation is in the range of 5 GB (and increasing
) 
Please Log in or Create an account to join the conversation.
Moderators: support
Time to create page: 0.070 seconds