 |
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Markus Halttunen - 02 Apr 08 15:31
Raising the severity to high. Sometimes I have to reopen the project many times to get this fixed. And my project has 30 modules so it is pretty painful to end up clicking "No, I don't want remove this module from the project" e.g. 60 or 90 times to be able to start working with the project..
 I had this happen to me a couple of times (on OS X) and was able to fix it by modifying the project file by hand. Could you attach your project file the next time this happens?
I sent the corrupted project files to Alexander.Chernikov@jetbrains.net. Please confirm that you got them.
The .com address worked better. I also sent a working version of the same .iws file so you should be able to compare the two to find out why the first one does not work. Hopefully you can get this very annoying problem fixed.
Any news about this issue? The problem is very annoying, it occurs very frequently and I have already provided you with a corrupted .iws file. Is there something else you need before you are able to move this issue forward?
Markus,
Thank you for the feedback. Unfortunately, I still cannot reproduce the bug. Just on the off-chance, you could try the following: 1. Clean IDEA caches. 2. Use the latest EAP build 7807: there were some minor fixes in path resolving. Maybe this will help. I will make more attempts. Here is a very simple project that is broken. Also with build 7807. As you can see, .ipr and .iml files are identical - the problem is in .iws.
Please note that this problem may be specific to OS X.
Raising the severity to extreme. The problem occurs to me even when I exit IDEA normally. It is so annoying I'm starting to become an Eclipse convert...
Alexander, what is the status of this issue?
I tried deleting fslogger in case it could have caused the .iws files to get corrupted but unfortunately it did not help.
Tested attached projects on Mac OS X 10.5.2, after force quite from IDEA. Everything is Ok, both projects open successfully.
Going on thinking. The attached project files do not even open correctly on my machine. They are already corrupted by using the force quit. Very strange..
I am also using Mac OS X 10.5.2. Interestingly, I was unable to reproduce the problem myself anymore with the attached project files. I can, however, still easily make it happen again. I'll see if I could attach some new corrupted project files tomorrow.
It really seems I can't reproduce the problem at will anymore. Perhaps deleting fslogger made a difference after all? I have seen it happen a couple of times in my actual work project, though. I'll keep you updated if I get any more details or can produce a broken example project again.
I still do get this all the time one my main project. I tried to reproduce the issue on a smaller project and it wasn't as easy but I managed to do it. I basically caused a crash, zipped the directory and then tried to open the project file. However, when I managed to get a corrupted project file, I unzipped the the directories I had stored earlier and tried again. This time the project file opened just fine.
So summa summarum. The problem does happen, and it seems to be more frequent on bigger projects. However, it seems that the corruption isn't in the project files at all. Perhaps IDEA caches get corrupted somehow? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Open
Cannot Load Module file $PROJECT_DIR$
