debugging extremely slow

Use this forum to ask questions after your subscription maintenance expires or before you buy. Need information on licensing or pricing? Questions about a trial version? This is the right place for you. No scripting questions, please.
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
This topic is 3 years and 2 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
User avatar
remkow
Posts: 18
Last visit: Tue Jan 11, 2022 4:26 am

Re: debugging extremely slow

Post by remkow »

whilst editing a script that I debugged a couple of times I noticed two things:

1) I was getting out of memory error exceptions during the script
2) editor was responding very slowly, e.g. half second to a second delay when typing a letter
3) task manager shows powershell studio is using 1,3 GBs of memory (active working set).

This may or may not be related to the issue I'm experiencing...
screenshot.png
screenshot.png (8.49 KiB) Viewed 9021 times
User avatar
remkow
Posts: 18
Last visit: Tue Jan 11, 2022 4:26 am

Re: debugging extremely slow

Post by remkow »

Is there any update on this?
User avatar
Alexander Riedel
Posts: 8479
Last visit: Thu Mar 28, 2024 9:29 am
Answers: 19
Been upvoted: 37 times

Re: debugging extremely slow

Post by Alexander Riedel »

You mixed two issues in one post, so not sure which one you mean. :D

The XML problem has been traced to PowerShell being extremely slow when querying the object hierarchy of the XMLDocument object.
A remedy is in QA. Realistically, it won't appear until after the holidays.

Merry XMas.
Alexander Riedel
SAPIEN Technologies, Inc.
User avatar
remkow
Posts: 18
Last visit: Tue Jan 11, 2022 4:26 am

Re: debugging extremely slow

Post by remkow »

Yeah the question was if the high memory usage/ out of memory errors were related or perhaps being the root cause.

Do you want me to open a seperate issue for the high memory usage?
User avatar
Alexander Riedel
Posts: 8479
Last visit: Thu Mar 28, 2024 9:29 am
Answers: 19
Been upvoted: 37 times

Re: debugging extremely slow

Post by Alexander Riedel »

I could not replicate it, but it is probably an effect of the XML issue. Let's see when you get the next build if this happens again.
Alexander Riedel
SAPIEN Technologies, Inc.
User avatar
remkow
Posts: 18
Last visit: Tue Jan 11, 2022 4:26 am

Re: debugging extremely slow

Post by remkow »

I just updated to the latest version (5.7.182) and it hasn't resolved this issue, is there perhaps a timeline for this fix?
User avatar
Alexander Riedel
Posts: 8479
Last visit: Thu Mar 28, 2024 9:29 am
Answers: 19
Been upvoted: 37 times

Re: debugging extremely slow

Post by Alexander Riedel »

As I indicated, after the holidays. Nothing has been released yet in 2021. We just came back from a break. Please stand by.
Alexander Riedel
SAPIEN Technologies, Inc.
User avatar
remkow
Posts: 18
Last visit: Tue Jan 11, 2022 4:26 am

Re: debugging extremely slow

Post by remkow »

Does 5.8.183 contain a fix for this issue?
User avatar
brittneyr
Site Admin
Posts: 1655
Last visit: Thu Mar 28, 2024 1:00 pm
Answers: 39
Been upvoted: 30 times

Re: debugging extremely slow

Post by brittneyr »

Yes, there were changes made to our debugger that should improve the speed in service build 5.8.183.
Please let us know if this works for you now.
Brittney
SAPIEN Technologies, Inc.
User avatar
remkow
Posts: 18
Last visit: Tue Jan 11, 2022 4:26 am

Re: debugging extremely slow

Post by remkow »

First test is looking good, will do some more testing with large files and report back here!
This topic is 3 years and 2 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.