Comment #1 on issue 25542 by [email protected]: model associator can accidentally believe LoadAssociations was successful, but it wasn't http://code.google.com/p/chromium/issues/detail?id=25542
I think the real issue is that we lose the sync changes corresponding to bookmark model changes due to a crash or other abnormal exit of the process. But we can address this by making model associator check for this situation and rebuild associations. But this cannot be a full solution since we won't catch edits by that approach. May be we can make model associator also check for equality of bookmarks when it's loading associations. But that kind of defeats the purpose of persisting associations - to not rebuild every time since it's expensive. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
