02-16-2023 05:45 PM
Has anyone experienced sudden disappearance of the UCCX Editor while coding? Just lost a bunch of code as it went missing in front of my eyes without any errors or crash report from Windows.
Solved! Go to Solution.
02-22-2023 12:52 AM
Solved the issue myself again. The logs turned out pretty helpful again.
When the Editor runs out of heap memory, it just closes out in a "disappearing act".
Not very nice at all!
And according to Cisco 95.31MB is all we get. I feel I am back in the early 90's where MB ruled.
02-16-2023 06:43 PM
I've seen random things like that, but not in the 12.x release. Do you have multiple CCX editors installed? Honestly, save often is my best advice.
david
02-17-2023 03:27 PM
Two different environments. One with only this version installed. Another with several other versions. Happened on both.
Yes, manual saving as there is no autosave functionality implemented in the Editor. The issue is the "sudden", "no errors" behavior that's concerning. Something must've happened to the error/exception handling implementation of this version.
02-17-2023 07:17 AM
Are you running on Windows 10? And are you as a user part of the Administrator group?
02-17-2023 03:28 PM
Yes and yes.
02-22-2023 12:52 AM
Solved the issue myself again. The logs turned out pretty helpful again.
When the Editor runs out of heap memory, it just closes out in a "disappearing act".
Not very nice at all!
And according to Cisco 95.31MB is all we get. I feel I am back in the early 90's where MB ruled.
02-22-2023 07:53 AM
Glad to hear you found the root cause. So is the solution to not have very big scripts or too many scripts open?
david
02-22-2023 11:12 AM
My customer has an 85 page printout of a script - a monster, so pretty much leaves me no option but to try to load it and break it down into sub flows, etc. I am doing an optimization is the intended purpose of the project.
I would say watch out that heap memory bar at the bottom to not turn red.
02-22-2023 10:24 AM
@mateev.borislav wrote:Solved the issue myself again. The logs turned out pretty helpful again.
When the Editor runs out of heap memory, it just closes out in a "disappearing act".
Not very nice at all!
And according to Cisco 95.31MB is all we get. I feel I am back in the early 90's where MB ruled.
Where did you get those logs?
In case anyone else is curious, Matedev's web page screenshot came from:
02-22-2023 10:44 AM
Maybe Cisco can help you expand the memory size? I know the attached defect is for the UCCX engine, but apparently Cisco TAC had special ability to expand memory for UCCX engine, perhaps there's something similar for the editor?
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuf79940
02-22-2023 11:18 AM
Correct. I've worked with Cisco a couple of times on increasing the JVM heap memory on the UCCX server to accommodate the engine java code.
I am opening a TAC case to see if there is any way to increase the heap memory on the Editor. If the Editor was a Java jar it would've been easier to adjust heap memory but Cisco compiled it into an executable so either they have an undocumented run parameter for that or they have to recompile the Editor with more heap memory allocated for it.
Will keep updating as I hear back from TAC.
02-22-2023 11:20 AM
The logs are located in the "log" folder in the install folder of the UCCX Editor.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide