Community
Participate
Working Groups
Periodic problem ---------------------------------------------------- Problem occured Periodic workspace. has encountered a problem. An internal error occured during: "Periodic workspace save." ---------------------------------------------------- An internal error occurred during: "Periodic workspace save.". Cannot set lower sequence number for root (previous: 12, new: 11). Location: C:\Dropbox\AndroidEclipse\.metadata\.plugins\org.eclipse.core.resources\.safetable\org.eclipse.core.resources ---------------------------------------------------- I uses DROPBOX for save my all projects. Sancs.
Can you please attach .log file from your workspace/.metadata folder? Please answer also the following questions: 1. How many people use your projects on dropbox? 2. Is it used at the same time by more than one user? 3. Do you share only projects or the whole workspace folder? 4. What is your Eclipse version? 5. What additional plugins are installed in your Eclipse instance? 6. What had happened just before the error occurred? Thanks!
It seems that master table in your workspace is corrupted. Can you please attach the .metadata folder from the affected workspace if the problem still occurs?
Let's try to fix it in 4.4.
As mentioned in bug 149121 comment 50, there should be only one instance of master table to avoid stale cached data. Fixed in master: http://git.eclipse.org/c/platform/eclipse.platform.resources.git/commit/?id=74758a62c4f8da5c9fc98aff832dfa08de41813a
Are there any workarounds?
(In reply to Endre Stølsvik from comment #5) > Are there any workarounds? There are no workarounds, because this error message is a good thing. It tells you that for some reason your workspace was in a bad state and this error message prevented your workspace from being corrupted. The fix that tries to prevent from that bad state was already pushed to master and is available in Eclipse 4.4 M2. You can download it here: http://download.eclipse.org/eclipse/downloads/ If you know steps how to reproduce on demand the error message mentioned in comment 0 please let me know.
CQ:WIND00-WB4-2543 Thanks for the detailed analysis. Some of our users have also seen this, and now we can tell them that the message is a good thing.
(In reply to Martin Oberhuber from comment #7) > Thanks for the detailed analysis. Some of our users have also seen this, and > now we can tell them that the message is a good thing. If you can get any additional information about circumstances when this happens, please let me know.
Created attachment 240845 [details] Zipped Logs Zipped Logs attached. Our user wrote: " I encountered the same error. The Details in the dialog says: An internal error occurred during: "Periodic workspace save.". Cannot set lower sequence number for root (previous: 6, new: 3). Location: G:\wrinstalls\vx7-20140307\workspace\.metadata\.plugins\org.eclipse.core.resources\.safetable\org.eclipse.core.resources I'm adding my workbench logs. wblogs-periodicsave.zip I don't remember exactly what I was doing when this happened. I was on a Webex showing Workbench and working with the Layer Project when it happened. "
Hi, I encounter a similar error in an RCP application, built with Eclipse 4.5. It happens a bit randomly, and it is quite annoying to say the least. I understand it is a good thing, but is there any way to make it a silent warning rather than a pop-up that gives our users the feeling something is going wrong… ? Cheers Alexis
(In reply to Alexis Drogoul from comment #10) > Hi, > > I encounter a similar error in an RCP application, built with Eclipse 4.5. > It happens a bit randomly, and it is quite annoying to say the least. I > understand it is a good thing, but is there any way to make it a silent > warning rather than a pop-up that gives our users the feeling something is > going wrong… ? > > Cheers > Alexis This exception prevents from workspace corruption so it is important to let the user know about it. If users have the feeling something is wrong, then they have good feeling because it is a very serious problem. It used to cause data loss in case users hadn't known how to recover properly corrupted workspace. If it happens when you can't do anything to fix it like during startup, then only a warning to the log file is written. Otherwise, an error dialog is appropriate, like in case of other serious problems e.g. OutOfMemoryErrors. If you can reproduce this problem with 4.5 or later, please open a new bug and provide steps how to reproduce it, e.g. with plugins from your RCP application or sequence of steps leading to this exception that will allows us to investigate what's happening there. We don't know much about circumstances when this error happens, so any help to track it is much appreciated.
Recently we encounter same exception. The root cause was two eclipse instances which used same workspace location. The workspace was located in NFS shared storage and seems WS/.metadata/.lock file protection does not work in this case. Regards, Krasimir kostadinov
