I ma using Intellij Idea Community Edition 2018.3.6 . Its behaving very slow suddenly. I tried updating the idea64.exe.vmoptions with the below values.
-Xms128m
-Xmx8192m
-XX:ReservedCodeCacheSize=240m
It didn't help.
I am using JRE1.8.0_152
Please suggest.
Please contact the support team with the CPU snapshot attached.
One of the known issues is the antivirus, but it mostly affects the startup. If it's slow during the regular work, it could be something else and only the CPU snapshot can help to identify the root case.
I can also suggest upgrading to the current version and see if it works better for you.
Related
I have a radio button that is represented as a pbdatawindow, when I run setcelldata to pick an option it works fine on my laptop but fails on my colleagues laptop. If we try the run the command again on my colleagues laptop we get a fatal error from UFT.
The only difference between my UFT install and my colleagues is that my colleagues version is installed in French. Has anyone seen a similar issue?
PbWindow().PbDataWindow().SetCellData 1,1,""
Few things to try:
What version of uft are you using? - perhaps check for newer of see if there is a patch available?
Jump onto the microfocus knowledge base and see if there is anything around power builder.
You say the machines are the same but does that include every application too? In the past I've known that if you install applications after uft it can break its references. Try uninstalling and reinstalling uft. There is a repair option but uninstall/reinstall is normally more thorough.
Try and clear out all your temp and user settings.
In your user profile backup then remove all folders with mercury, hp, Hewlett-Packard and microfocus.
-The go to %temp% and clear evetything.
Try and pin down the problem - Has your colleague tried the English version or uft? - if that works, is it an option? (everyone use the same version)
If it doesn't work it suggests it's your colleague's machine as opposed to uft.
Is evetything such as the resolution and browser/application versions the same? Or simply try another French localised machine?
What's the fatal error? Does it provide any clues on why it failed?
Finally, You're paying a lot for commercial software. Don't suffer in silence :-)
Log a support call with microfocus. It's a bit long winded but Back in the day they used to be pretty good at helping. They'll ask you for logs and knowing how to get that is good to know.
There's more to try - let me know how you get on.
The program collects data about 3-5s when it gets the parameter values
But using idea's own debug startup is fast
My IDEA version is 2020.1, and my JREBEL version is 2020.2.2
I searched for the cause of the problem, and someone said jdk version 1.8 localhost, and I tried to fix it, but that's not the problem I had
If you have any experience to help me, please feel free to say thank you
I feel like I'm experiencing a common problem, but I wasn't able to find anyone asking about it.
As the title indicates, we're forced to use AccuRev for SCM. We have our development stream under our QA stream. Let's say we're working on a big project that will be in QA for weeks before being released (we're following a scrum strategy). In the meantime, there's a bug fix that needs to go out before this big project. The problem is the bug fix affects some of the same files the big project uses. How would I get my files from development to production, without bringing the big project with me?
Sorry, I hope that makes sense!
Thanks!
If you are using the change package feature in AccuRev, you can select that issue and just promote those changes into the production stream.
Otherwise, you will need to determine the promote transaction(s) of the of the bug you fixed in development and change palette those fixes into production.
I think I found a solution that will work for us.
I plan on creating a snapshot off of the development stream after each successful deployment to production. Bug fixes/smaller projects will work off of this snapshot. That way I can keep anything I'm currently working on in DEV from getting inherited into my bug fix. When I'm ready to deploy my bug fix, I'll create another snapshot and re-parent my big project there. Then I'll revert the change package in QA and development, re-parent my bug fix to development, and promote as normal.
It's a slightly modified version of what's explained in this article: https://accurev.wordpress.com/2008/03/27/pattern-for-stable-development/
I only just discovered that show UML Diagrams no longer works in IntelliJ 12.0.3.
Does anyone know whether there is a problem with it? Or whether it has been intentionally removed?
ps: It still works fine in 11.1.5.
I tried it and experienced the same as you.
The feature is disabled, and must be enabled by checking "UML Support" under File->Settings->Plugins
Ok, I've found out that Ctrl+Alt+U works in 12.0.3 Ultimate Edition, and not in the Community edition.
I love Aptana, but sadly it crashes on me almost every day. I'm stubbornly sticking with the editor, but if I can find and fix the instability, I will have no major complaints with it.
I'm running Aptana Studio 3, build: 3.0.9.201202141038 but the crashing has been ongoing ever since I installed Aptana 3 many months and many version upgrades ago. Following the most recent crash I checked the Aptana .log but there was nothing valuable in there. There was however quite a bit of info in the OS-X "view details" notification following the crash: http://pastebin.com/02JrqrUQ
Sometimes it crashes following SVN actions, but also, as most recently, it will crash when it's just sitting there.
I'd appreciate any suggestions on how I can address this issue. I believe that I previously
had tried a reinstall which didn't fix the issue, but if no one has anything else to try, I guess I may give that a try again.
Thanks,
Dan
---- UPDATE ---
Ingo, Thanks for the response. That thread on appcelerator.org definitely describes the errors I was seeing.
Following your advice, I upgraded to the Aptana nightlies (now on version 3.1.0) and have not seen a crash in 2 full days. Hopefully any future crashes will now be few and far between and no longer a daily occurence.
Thanks so much for the response.
Thank you very much for your information. We've been tracking this issue, but honestly, it's been a bear to diagnose and reproduce, since most of the references don't point to any code of Studio--only the underlying versions:
https://jira.appcelerator.org/browse/APSTUD-3682
Please follow along on the linked ticket for more information. You might try the latest nightly (3.1 version) at preview.appcelerator.com which is built on top of Eclipse 3.7.
I had this same issue - and then I could not even open Aptana. Right click on the program -> click Properties -> Compatibility (Windows 7) > and tick "Run this program as an administrator"
This worked for me temporarily - the real fix is to delete or rename the .log file in your workspace.