MPLAB X v4.20缓慢还是悬挂？

我尝试了它，打开/编译了一个PIC32的项目，并且看起来大致相同的Posi4GB XP Java 1.8。



      以下为原文

    I tried it quickly, opened/compiled a project for a pic32, and looked more or less the same usual stuff
 
4GB XP java some 1.8

为我工作，与以前版本相同。Windows 10 x64，1803。MPLABX 4.20，PIC24项目。（和两个不同的PC）



      以下为原文

    Works for me, same as previous versions.
Windows 10 x64, 1803. MpLabX 4.20, PIC24 projects.  (and two different PCs)

同样使用4.20，运行超高速.Wi764位，16GB RAM，1TB SSD和CPU时钟到3.8GHz。几个星期前，我格式化了我的PC，并做了一个全新的安装。



      以下为原文

    Also using 4.20, runs super-fast.
Win7 64bit, 16GB ram, 1TB ssd and cpu clocked to 3.8GHz.
 
A few weeks ago I formatted my pc and did a fresh install.

在这里看来性能不错，双XEON E5-2696V2（24内核，48线程总计）64 GB RAM，Windows 10 X64，2TB SSD。不是你需要所有这些核心，但是如果你有一些项目打开它肯定加快了加载和编译；



      以下为原文

    Seems OK performance-wise here, dual Xeon E5-2696v2 (24 core, 48 thread total) 64GB RAM, Windows 10 x64, 2TB SSD. Not that you need all those cores, but if you have a number of projects open it sure speeds up the loading and compiling ;-)

在我的结尾没有这样的行为（至少，没有比正常情况更迟缓）了。我正在运行一个i5-3550W/Windows 7 x64，我的工作站用8GB的RAM，现在不是一个懒散的，但也不是很大的一个。我应该拿起更多的RAM，如果我同时运行MPLAB X和Visual Studio，事情开始变得不可靠了。



      以下为原文

    No such behavior on my end (at least, no more sluggish than normal). I'm running an i5-3550 w/ Windows 7 x64 with 8GB of RAM for my workstation so not a slouch but not much of a powerhouse either nowadays.
I should pick up some more RAM though, things start to get dicey if I'm running MPLAB X and Visual Studio at the same time...
 

…取***卡；



      以下为原文

   
.. and de-fluffed the video card ;)
 

你认为它不能进入那种状态，我现在用水冷却。



      以下为原文

    You re-membered
Didn't think it could get in that state.
I use water cooling now.

嗨，这个线程中的大多数似乎没有V4.2的问题？长期以来，MPLAX X的用户从4.15升级到4.2，安装好了，重新启动PC，ISASUS Windows 10 64位全部达到数据。8GB内存。4.2启动，打开一个项目，然后什么也不做。鼠标可以通过MPLAX X，但什么也不能做。进度条显示“打开项目”，但棒不继续。使用任务管理器关闭4.2和JavaW.EXE。重新启动同样的结果。删除4.2个缓存，仍然不会启动。今天大部分时间都没有安装和重新安装V4.2在Windows ER中。RoR日志显示Java8对Windows停止响应。在任务管理器JavaW中，占用大约0.1%的CPU时间，使用370MB内存。MPLAB X 4.15仍然运行正常，因此将恢复到该版本。如果没有修复程序，V4.2不能再浪费时间，那么在重新升级之前必须等待下一个版本。东北人



      以下为原文

    Hi,
most in this thread seem to have no problems with V4.2?
 
As a long time user of MPLAB X today I tried to upgrade from 4.15 to 4.2.
 
Installed OK, restarted PC which is ASUS Windows 10 64 bit all up to date.
8 GB memory.
 
4.2 starts, opens a project and then does nothing. Mouse can go over MPLAB X but can do nothing.
Progress bar shows "Opening Projects" but sticks does not continue.
Shutdown 4.2 & javaw.exe using Task Manager - Restart again with same result.
 
Deleted 4.2 Cache, still wont start.
Spent most of today un-installing and re-installing V4.2.
In Windows error logs it appears that javaw 8 stops responding to Windows.
In Task Manager javaw is ticking over taking very little CPU time around 0.1% and using 370 MB of memory.
 
MPLAB X 4.15 still runs OK so will revert to that version. Cannot waste anymore time on V4.2 if no fixes are available then will have to wait for next version before trying to upgrade again.
 
Anyone with similar problem or with a solution please respond?
 
Northeastman

您可能能够从MPLAB X日志记录功能中获取更多信息。我认为这是选项& Gt；嵌入式和GT；诊断？至少你可以通过支持票把结果发送到微芯片上，看看他们说了些什么。



      以下为原文

    You might be able to get some more info out of the MPLAB X Logging function.
I think it's Options>Embedded>Diagnostics?
 
At the very least you could send the results to Microchip via a support ticket and see what they say.

KTrenholm，谢谢你的建议，但是一旦挂起4.2，就无法访问该菜单或命令，因此无法访问日志。在任何情况下，我的经验告诉我，日志生成的选项必须在生成日志之前打开，因为我不能获得4.2接受任何命令…“catch 22”，除非日志在安装过程中作为文件保存在某个地方，否则我不能发送它。空间或其他奇怪的字符在其构建中，我总是安装到文件夹C:Microchip  MPLABX…而不是默认的“c:程序文件（x86）”，这显然包含空格和其他“怪异字符”。不确定为什么这应该是MS默认值，当它们在构建中警告空间等等时！我认为这是一个可爱的陷阱，新手和人们试图使用MPLAX X首次使用这些文件夹时，他们的第一次项目。几年前，我曾在前一篇文章中评论过这一点，（旧论坛），但MS从未更改默认文件夹，所以现在我将它作为例程来更改。如果能修复，我会很高兴地把一张票发送给MS。非常感谢您的建议，我非常感谢YO。你需要时间来回应。东北人



      以下为原文

    KTrenholm,
thank for your suggestion but once 4.2 hangs there is no access to that menu or command so no access to the log. In any case my experience tells me that the option for logging has to be switched ON before the log is generated and since I cannot get 4.2 to accept any commands...."Catch 22"
 
Unless the log is saved as a file somewhere during installation I would not be able to send it.
 
Due to "Make" not accepting spaces or other weird characters in its build I always install to a folder C:MicrochipMPLABX... instead of the default of "C:Program Files (x86) " which obviously involves spaces and the other "weird characters". Not sure why this should be the MS default when they warn against spaces etc in the build!  I think it is a lovely trap for newbies and people trying to use MPLAB X for the first time when using these folders for their first time projects. I have commented on this in a previous post some years ago, (Old forum) but MS have never changed the default folder, so now I change it as a routine.
 
I would be very happy to raise a ticket and send the log to MS if it would result in a fix.
 
Thanks very much for the suggestion and I do appreciate you taking the time to respond.
 
Northeastman

它可能是一个拉伸（我不知道这个设置是否会继续），但你可以尝试卸载4.20，回到你以前的版本，设置日志记录，然后重新安装4.20，并在安装程序中选择保持你的设置从4.15，当然，如果这是设置之一。在进行中。



      以下为原文

    It might a stretch (I don't know if this setting would carry over), but you could try uninstalling 4.20, going back into your previous version, setting up the logging, then reinstall 4.20 and choose in the installer to keep your settings from 4.15.
 
That is of course, if that's one of the settings that carries over.

KTrnholm，好主意，但我真的没有时间用MPLAB X 4.20进行实验，必须继续做一些实际的工作。如果时间允许的话，我会试试你的建议。事实上，我不记得有什么选择可以进行任何设置了吗？第一次安装时，我得到了持久性文件夹的通常选项，这是我接受的，但是随后的安装并没有出现这样的选择，这似乎意味着卸载过程中遗留了什么东西。也许来自MS的人会知道是否有安装日志之类的东西，或者至少如何彻底清理MPLAX，缓存文件夹和其他所有的东西？再次，非常感谢你的时间。东北人



      以下为原文

    KTrnholm,
nice idea, but I am really out of time experimenting with MPLAB X 4.20 and must get on with some real work.
 
If time allows I will try your suggestion. Actually I don't remember being given the option to carry forward any settings? First time I installed I was given the usual option for persistence folders, which I accepted, but subsequent installs did not come up with that choice, which seems to imply something got left behind during the uninstall?
 
Maybe someone from MS will know if there is such as thing as an install log, or at least how to completely clean MPLAB X, cache folders and all others?
 
Again, thanks very much for your time.
 
Northeastman

在这里找到日志文件，它们总是被写入。（我不知道是否存在不同的级别）C:用户…AppDATarimeMPLABIDIDDEVV4.20var 日志，但是它们“复杂”到足以将您的非工作4.2与工作4.15日志文件进行比较，这需要时间。如果你对4.15是满意的，这将不会得到回报。你的Java内存占用大约300 MB似乎表明它被卡在“早期”。你在这里找到其他MPLABX或Net Bebean配置：C:程序文件（x86） Microchip  MPLABX  V4.20MPLABB平台 EtCyes，并且我确认有许多不同的日志记录级别。它仍然记录了我提到的启动日志文件，甚至日志记录级别关闭。您可以在这些文件夹中找到一些XML配置的日志记录级别设置。



      以下为原文

   
 
 You find the log files here, and they are always written. (I don't know whether there exist different levels)
    C:Users ... AppDataRoamingmplab_idedevv4.20varlog
However they are "complex" enough that you would need to compare your non-working 4.2 with a working 4.15 log file, which takes time. If you are happy with 4.15 this will not pay off.
Your small Java memory footprint of some 300 MB seems to show that it is stuck "early".
 
And you find other mplabx or net-beans configuration here:
   C:Program Files (x86)MicrochipMPLABXv4.20mplab_platformetc
 

yes it is, and I verified that there are many different logging levels.
Still it writes the startup log file I mentioned even with Logging Level OFF.
You could find the Logging level setting probably in some xml configuration in those folders.

无法编辑以前的文章：由各种日志记录级别写入的日志文件（默认值为OFF）引用这些选项中具有可配置路径的日志文件。因此，这并不涉及所述的消息。



      以下为原文

    Cannot edit previous post:
The log file written by the various logging levels (default = OFF) refer to a log file with configurable path also in these options.
So this does not refer to the mentioned  messages.log.* file(s), which are always written.

嗨，罗尔夫，谢谢你的贡献。V4.20关闭V4.20使用Windows 10“程序和特征”检查目录并删除所有引用到V4.20，即C:UsvsAppDATAB\ROMAMMPLABIDIDDEVV4.20C:\用户\用户名AppDATABStudio MPLABIDIDCache DEVV4.20删除原始下载文件MPLABX-V4.20 WiDOWS安装程序。ExeDouthLoad加载一个新的CopyOnter 4.15，并设置日志以在4.15Cald4.15Run安装4.20中使用新的下载来配置。安装程序显示消息：请在安装之前关闭MPLABX的所有实例。在任务管理器中仍然有一个MPLABIDEID.exe（32位）运行吗？看到这之前，有时有一个以上的坐在进程列表。安装V4.20现在安装OK安装到C:Microchip  MPLABXV4.20.RealEnter PCRUN V4.20，并从V4.15导入设置——这需要很长的时间，但是现在开始了。日志级别仍然显示为配置文件，V4.20文件已经发送到C:UpvestUrrNeAppDATaroAIMMPLABIDIDDEVV4.15VARLOGMPLABX4.4.XML.最后一切都在工作。感谢所有贡献了这些有用的回复的人，我们希望以上程序能帮助任何有类似问题的人。



      以下为原文

    Hi Rolf,
thanks for your contribution. We finally got V4.20 to work using the procedure below.
 

• Close V4.15
  
• Uninstall V4.20 using Windows 10 “Programs and Features”
  
• Examine directories and delete all references to V4.20 i.e.
  C:UsersusernameAppDataRoamingmplab_idedevv4.20
  C:Users username AppDataLocalmplab_ideCachedevv4.20
  
• Delete original download file MPLABX-v4.20-windows-installer.exe
  
• Download a new copy
  
• Open 4.15 and set logging to CONFIG
  
• Close Projects in 4.15
  
• Close 4.15
  
• Run install 4.20 using new download.
  
• Installer shows message: Please close all instances of MPLABX before installing. Look in Task Manager there is still an mplab_ide.exe(32 bit) running? Seen this before sometimes there is more than one of these sitting in the Processes list. Stop this task running.
  
• Install V4.20 now installs OK install to C:MicrochipMPLABXv4.20.
  
• Restart PC
  
• Run V4.20 and import settings from V4.15 – takes a very long time to do this but now starts.
  
• Logging Level is still showing as CONFIG in V4.20 files have been sent to
  C:Users username AppDataRoamingmplab_idedevv4.15varlogMPLABX4.15.xml
  

Finally everything is working.
 
Thanks to all who contributed the helpful replies, and we hope the above procedure will assist anyone else who has a similar issue.
 
Northeastman
 
 

我也有同样的问题，昨天我从V4.01更新了。在安装和导入设置之后，它试图打开上次在V4.01中使用的项目，但它挂起。所以我卸载了它，启动了V4.01，关闭了项目，重新安装了V4.20，启动了它，并打开了我的项目。它奏效了。但今天我也有同样的问题。没有机会打开项目或做任何事情。我将切换回V4.01，并等待更好的版本在未来！！！！！！！！！！也许这取决于这个项目，我有一个C/C18汇编的混合C/C项目，沃纳



      以下为原文

    I have the same problem. 
Yesterday I updated from V4.01. After installing and importing settings it tries to open the project I used last time in V4.01 but it hangs.
So I uninstalled it, started V4.01, closed the project, reinstalled V4.20, started it and than opened my project. It worked. But today I have the same problem. No chance to open the project or to do anything.
I will switch back to V4.01 and wait for a better version in future!!!!!!!!
Maybe it depends on the project, I have a mixed C/assember project with old C18 compiler
Greetings,
Werner

和我一样，安装在Windows 7上的Windows 10。但是它在Windows 2016，新安装上没有问题。它挂在另一台带有Windows 7的笔记本电脑上。MPLAB X冻结了，唯一能做的就是杀死任务管理器中的Java进程。我试图删除在生成、调试、DIST文件夹、NBPix/*.MK文件、NBPix/Buy/*.*中生成的所有文件。有时这有助于但并非总是如此。今天上午，它没有帮助，看到其他人遇到同样的问题，我决定留下4.15，直到有一些反应从Microchip。P.S.看来MPLAB X 4.20是第一个版本，将与新的2版本的XC编译器。添加一个选项来选择C标准-C89、C90或C99。此选项不存在于4.15 IVAN中。



      以下为原文

    Same to me, on Windows 10 that is installed over Windows 7. However it works without problems on Windows 2016, fresh install. It hangs on another laptop with Windows 7 on it.
 
MPLAB X freezes and the only thing that can be done is to kill the java process in Task manager.
 
I tried to delete all generated files in build, debug, dist folders, nbproject/*.mk files, nbproject/private/*.*. Sometimes this helped but not always. This morning it did not helped, and seeing that other peoples meet the same problem, I decided to stay with 4.15 until there is some reaction from Microchip.
 
P.S. It seems MPLAB X 4.20 is the first version that is going to work with the new 2.0 version of XC compilers. An option is added to select C standard - C89, C90 or C99. This option is not present in 4.15.
 
Ivan

我在启动时也有类似的问题。我正在运行Windows 10 Pro 64位。我可以通过重命名我的项目来摆脱这个问题，所以MPLAB不会尝试打开它，然后关闭MPLAB并重新启动它，最后再次打开我的项目。



      以下为原文

    I've had similar problems with hangs on startup. I'm running Windows 10 Pro 64-bit. I was able to get past the hang by renaming the my project so MPLAB wouldn't try to open it, then shutting down MPLAB and restarting it, and finally opening my project again.