Forum Discussion
Hi Sanjay,
Mobsync is not part of our application under test and it is not necessary to run this process during execution.
Thanks,
Priya
Hi,
So there are two possible solutions.
1. During / Before the Start of your script kill the mobsync process from taskmanager. This you can achieve through scripts. Can you confirm whether this process starts automatically after killing?
2. Or allow this process to run. Write an event handler code on unexpected windows and close the dialog that pops up.
- priyaram8 years agoOccasional Contributor
Hi,
After closing mobsync process sometimes it will pop-up again and continuous closing after 3 to 5 times we are getting out of system resource error.
If 'Out of system resource' error popped continuously, execution will not be proceed further. In this case, we don't have any option other than terminating TC/TE.
- sanjay02888 years agoFrequent Contributor
The only option what I see is to uninstall mobsync from the computer where you are running automation test scripts.
If you have plenty of time to invest on disabling mobsync then probably you can try your luck with the solutions provided in the link mentioned below
- Colin_McCrae8 years agoCommunity Hero
I don't think TC/TE itself is the problem. The error causes a failure in the runtime library which TC/TE presumably ALSO uses. But it's not the one causing the error.
You need to fix mobsync. If something is triggering it again after you disable, you need to work out what and fix it.
More suggestions here: https://answers.microsoft.com/en-us/windows/forum/windows_vista-performance/disabling-mobsyncexe/399f06f6-930e-40ee-90d9-fb470d1178fb
But I think you're asking in the wrong place.
TC/TE (as far as we can tell) is not CAUSING the problem (although, as I already said, your tests might be - but we don't know that as we have no idea what you're tests are doing), mobsync.exe is. TC/TE is being AFFECTED by it.
I've provided a link. So has sanjay0288. But it's not a TC problem. You'll need to fix your PC basically! Google is your friend ....
I wouldn't bother with event handlers and things to try and catch and kill the process. Unless your event handler runs VERY frequently, it will probably still get far enough to error out at some point. It would only be a sticking plaster. And probably not a very good/reliable one.
- priyaram8 years agoOccasional Contributor
Hi,
Yes its not a problem with TC/TE. We don't know why this process is running after disabling offline files and it occurs in different scenarios.
Probably this is due to low memory for operating system to complete a _beginthread or _beginthreadexcall, or thread local storage has not been initialized by _beginthread or _beginthreadex as pointed in "https://msdn.microsoft.com/en-us/library/d509d9f9.aspx".
But we have machines configured with 8 GB RAM and 2 core intel processor.
We need to identify for which thread this error has popped up. As a temporary solution to proceed with execution we have implemented to handle in Unexpected window event. But this also sometimes will lead to 'Out of system resource' error.
Related Content
Recent Discussions
- 15 hours agotramuntana
- 3 days agoSlickRick