My wonderful corporate Dell crashed when "hibernating", and now NetBeans freezes when launching. (It displays the full interface, and starts "Scanning Projects", but doesn't get past there and I can't click on anything.)
I imagine there's some cache somewhere to clear out or something. Anyone know where?
I kinda had that type of problem before. What I end up doing to resolve that problem is to remove all the project entries that were loaded but not closed when I closed the problem. They are in:
.netbeans/6.X/config/Preferences/org/netbeans/modules/projectui.properties
In the entries:
openProjectsDisplayNames.0=PROJECTNAME
openProjectsURLs.0=file:/PATH/TO/PROJECT
Related
The problem
Hi, I have been experiencing this kind of loading infitely on the window screen: "Application.Reload" since two or three days ago. This just happened spontaneously without any reason. I have been seaching for a solution, but the uniques fixes i had found are not working for me.
The unique not permanet solution that I came up is just use the Task Manager and close up Unity.
The possible fixes that I have tried:
"Just locate the project folder in the system explorer and click on properties" (This only work one time per application or maybe it just do not work.)
"You can check to see if there is any place in your project path that is not in English" (It just do not work.)
These are the fixes that I have tried.
Example of the problem
Meanwhile I am writing this question, I want to re-confirm this is a infinite load. So I open up my Unity Proyect, enter in the Play Mode and write this question.
This is the result:
https://i.stack.imgur.com/sTA48.png
Edit: the image actually shows the longest time i have been waiting. (1:48:34hs)
Thank in advance for any kind of help!
As I know, this problem persist as well in any Unity Operation, it can happen on Reload, Importing, Asset Indexer, etc. Is just a problem that doesn't affect Unity, and devs marked it as WNF (We'll Not Fix).
I have been struggling with this problem for some years now and the only solution I found was to close it from Task Manager and reopen it.
After last Ubuntu 14.04 kernel update (current one: 4.4.0-36-generic) when I open Eclipse (Luna) in a matter of few seconds it closes or freezes and then closes (I can be simply editing a comment, or even stop typing for some seconds and then it happens, so I think it can't be related to the code itself).
I personally prefer when it freezes first, so it gives you some seconds to mentally prepare of what is about to happen with your last-hour work.
No clue on system.log or /.../my_workspace/.metadata/.log of what is happening.
Where could I look to try to understand what is happening?
Is it possible that Eclipse closes without leaving any clue/crash-report of why is it doing that?
After trying a lot of possible solutions because Eclipse was crashing every 10 minutes I've found this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=465693
According to this bug report it is not an Eclipse problem but an Eclipse-JRE relationship problem.
Since I've modified several lines in eclipse.ini I cannot be sure about the solution, but it seems it was adding this line on it:
-XX:-UseLoopPredicate
I've been without crashes for more than 1 hour so far. However I'll wait at least one or two days before assuming this solution really works.
EDIT/UPDATE: Confirmed; it works like a charm.
Whenever eclipse crashes you will get hs_err_pid4612.log this kind of file
inside eclipse folder.
For fixing this issue :
Add this to eclipse.ini file:
-Dorg.eclipse.swt.browser.DefaultType=mozilla
I am using Eclipse Indigo v.3.7.2. For the past few weeks it has been really slow and keeps throwing not responding notification. Every time i click, scroll, type etc it freezes. I viewed the .log file but not sure what most of it means. I was told that there is an issue with the com.ibm.etools.webtools.json package and/or memory issues since cleanup is not getting done.
so my question is where do i find the above package? I tried opening the resource but it was not found. Also, how can I do a cleanup?
ty in advance..
I closed Eclipse because I had a feeling my PC was gonna crash (been acting funny today), and it said it saved my workspace and closed normally.
But when I went back in after reboot, my workspace wasn't loading - even after selecting the right one my projects wouldn't show and the layout was reverted to default....not such a big deal, just re-imported.
But... One of the source files I was working on seems to have been corrupted, replaced with one continuous line of squares, which is kind of a big deal :/
Any thoughts on what caused this? I know there's probably no chance of getting that file back, but if anyone has had a similar experience or knows what the jaysus happened that'd be cool! Ideally I'd like if this never happened again...
Problem was related to my SSD: Weird bug where after 5184 hours of use it would shutdown.
Firmware update fixes the problem.
More here: http://www.tomshardware.com/news/Crucial-m4-Firmware-BSOD,14544.html
I have had this problems for a couple of times but usually could solve it by an update. However, this fix does not work for me anymore.
Actually, two problems here:
The minor one: I have osX 10.8.3 and Eclipse Juno (M20130204-1200) installed. Since a good amount of time, it takes eclipse ~ 4-5 minutes to start up for the first time after the system start. Once it was closed and is re-opend again, it starts up quick. I think this problem came since apple started to mess around with the JRE? Does anybody also experienced this delay? Could it be that one of the installed plugins checks for updates and causes the delay?
The major one: after eclipse is fully up & running, I can not open .py files anymore. When I open my pydev project (btw. pydev 2.7.3), eclipse freezes and I need to kill the whole thing and restart. -> I can not use it for python coding anymore, which is my primary task...
Suggestions? Re-install eclipse maybe?
Thank you for suggestions,
El
Can't really comment on #1, but for #2, can you try attaching jvisualvm to see what's going on there? (and create a thread-dump and post it somewhere so that I can take a look at it).
I'd ask you to create a bug-report for that, but the new tracker is still not up (I hope I'm able to put it up right after the funding at http://igg.me/at/liclipse is finished).
The problem was resolved by following these steps. They essentially disable one
JRE.http://support.apple.com/kb/HT5559?viewlocale=en_US