Edge Workspaces sync BUG
Hello
First of all, I think that Workspaces in Edge is a very useful feature! Edge also has vertical tabs, which makes it the best tool for researchers using hundreds of tabs. I think other browsers can learn from this. With Workspaces, I can move windows I don’t currently use aside and open them again when needed without loading to RAM. Other browsers lack this feature, so I moved to Edge from Chrome. Edge is now my main tool for ongoing online research.
However, after some months of use, I see that there are bugs that make me frustrated. With Workspaces, Edge is slow, it freezes, fails to synchronize, and reverts changes.
It does not update tabs and moves new tabs to the end.
Let’s say that I have opened tabs: New Tab, facebook.com, A, B, C, D, E
Later, I open links in new tabs from New Tab, Facebook, and A and leave them open. The tabs are: New Tab, msn.com/F, facebook.com, G, A, A2, B, C, D, E
After some time, Workspaces synchronize, there is a short or longer Edge freeze. Then I see tabs are reorganized and F, G, H moved and changed addresses. The tabs are now: New Tab, facebook.com, A, B, C, D, E, New Tab, l.facebook.com/l.php?u=G, A2
It looks like Workspaces never update opened tabs when there was redirection through New Tab or l.facebook.com/l.php?u= or any other redirection on other websites. It only stores the first address it sees. When I refresh these tabs to see the description and go to the proper addresses, it still reverts it back! After I organize the order properly, it sometimes stays or is reverted back! This is frustrating when you need order and proper descriptions!
It is terribly slow, especially after opening another Workspace.
I also encountered long freezes of Edge when opening another Workspace window or at random, probably when it synchronizes (a red dot appears next to the workspace name). Sometimes I have to wait 5 minutes, sometimes 15 minutes, sometimes I’m losing patience! I have plenty of PC power (12-core Ryzen 3900X, 32GB RAM, Samsung SSD 970 EVO Plus 1TB) and when I check Process Hacker, I see that Edge isn’t using 100% of CPU, but still is frozen. I noticed that when it’s frozen, there are around 200 disk writes, fast changing, 9MB/s total:
C:UsersmeAppDataLocalMicrosoftEdgeUser DataDefaultSync DataLevelDB256443.ldb … ( edge_workspace_disk.xls )
When LevelDB writes stop, Edge is unfrozen.
I’ve given msedge.exe processes high priority, but it doesn’t solve anything.
I noticed this on previous versions starting from 122. I use Stable and Beta (to have two separate profiles) on PC and laptop. I waited hoping it will be solved, but nothing changed. It’s possible that developers only tested Workspaces with a limited number of tabs and not with power users like myself, who manage 10 workspaces with 200-600 tabs in each. The consistent unreliability suggests there may be unresolved bugs present in each version.
I examined the LOG.old file in the Sync Data>LevelDB folders of each browser and noticed that when a freeze occurs, there is a specific behavior logged:
2024/06/12-13:14:19.485 1a570 Generated table #365187@0: 40283 keys, 2109396 bytes
2024/06/12-13:14:19.485 1a570 Compacted 8@0 + 1@1 files => 2109396 bytes
2024/06/12-13:14:19.488 1a570 compacted to: files[ 4 6 7 0 0 0 0 ]
2024/06/12-13:14:19.489 1a570 Delete type=2 #365171
2024/06/12-13:14:19.489 1a570 Delete type=2 #365172
2024/06/12-13:14:19.489 1a570 Delete type=2 #365174
2024/06/12-13:14:19.489 1a570 Delete type=2 #365176
2024/06/12-13:14:19.489 1a570 Delete type=2 #365178
2024/06/12-13:14:19.489 1a570 Delete type=2 #365180
2024/06/12-13:14:19.489 1a570 Delete type=2 #365182
2024/06/12-13:14:19.489 1a570 Delete type=2 #365184
2024/06/12-13:14:19.489 1a570 Delete type=2 #365186
2024/06/12-13:14:19.491 179a0 Level-0 table #365197: started
2024/06/12-13:14:19.492 1a0a0 Current memtable full; waiting…
2024/06/12-13:14:19.500 179a0 Level-0 table #365197: 467718 bytes OK
2024/06/12-13:14:19.503 179a0 Delete type=0 #365194
2024/06/12-13:14:19.504 1a570 Level-0 table #365199: started
2024/06/12-13:14:19.505 1a0a0 Current memtable full; waiting…
2024/06/12-13:14:19.511 1a570 Level-0 table #365199: 467718 bytes OK
2024/06/12-13:14:19.514 1a570 Delete type=0 #365196
2024/06/12-13:14:19.515 179a0 Level-0 table #365201: started
2024/06/12-13:14:19.516 1a0a0 Current memtable full; waiting…
2024/06/12-13:14:19.524 179a0 Level-0 table #365201: 467718 bytes OK
2024/06/12-13:14:19.530 179a0 Delete type=0 #365198
2024/06/12-13:14:19.530 1a570 Level-0 table #365203: started
2024/06/12-13:14:19.531 1a0a0 Current memtable full; waiting…
2024/06/12-13:14:19.539 1a570 Level-0 table #365203: 467718 bytes OK
2024/06/12-13:14:19.542 1a570 Delete type=0 #365200
2024/06/12-13:14:19.542 179a0 Compacting 8@0 + 1@1 files
2024/06/12-13:14:19.556 179a0 Level-0 table #365206: started
2024/06/12-13:14:19.564 179a0 Level-0 table #365206: 467718 bytes OK
2024/06/12-13:14:19.568 179a0 Delete type=0 #365202
2024/06/12-13:14:19.572 179a0 Level-0 table #365208: started
2024/06/12-13:14:19.581 179a0 Level-0 table #365208: 467718 bytes OK
2024/06/12-13:14:19.584 179a0 Delete type=0 #365205
2024/06/12-13:14:19.588 179a0 Level-0 table #365210: started
2024/06/12-13:14:19.596 179a0 Level-0 table #365210: 467718 bytes OK
2024/06/12-13:14:19.600 179a0 Delete type=0 #365207
2024/06/12-13:14:19.604 179a0 Level-0 table #365212: started
2024/06/12-13:14:19.611 179a0 Level-0 table #365212: 467718 bytes OK
2024/06/12-13:14:19.615 179a0 Delete type=0 #365209
2024/06/12-13:14:19.620 1a0a0 Too many L0 files; waiting…
HelloFirst of all, I think that Workspaces in Edge is a very useful feature! Edge also has vertical tabs, which makes it the best tool for researchers using hundreds of tabs. I think other browsers can learn from this. With Workspaces, I can move windows I don’t currently use aside and open them again when needed without loading to RAM. Other browsers lack this feature, so I moved to Edge from Chrome. Edge is now my main tool for ongoing online research.However, after some months of use, I see that there are bugs that make me frustrated. With Workspaces, Edge is slow, it freezes, fails to synchronize, and reverts changes. It does not update tabs and moves new tabs to the end.Let’s say that I have opened tabs: New Tab, facebook.com, A, B, C, D, ELater, I open links in new tabs from New Tab, Facebook, and A and leave them open. The tabs are: New Tab, msn.com/F, facebook.com, G, A, A2, B, C, D, EAfter some time, Workspaces synchronize, there is a short or longer Edge freeze. Then I see tabs are reorganized and F, G, H moved and changed addresses. The tabs are now: New Tab, facebook.com, A, B, C, D, E, New Tab, l.facebook.com/l.php?u=G, A2It looks like Workspaces never update opened tabs when there was redirection through New Tab or l.facebook.com/l.php?u= or any other redirection on other websites. It only stores the first address it sees. When I refresh these tabs to see the description and go to the proper addresses, it still reverts it back! After I organize the order properly, it sometimes stays or is reverted back! This is frustrating when you need order and proper descriptions! It is terribly slow, especially after opening another Workspace.I also encountered long freezes of Edge when opening another Workspace window or at random, probably when it synchronizes (a red dot appears next to the workspace name). Sometimes I have to wait 5 minutes, sometimes 15 minutes, sometimes I’m losing patience! I have plenty of PC power (12-core Ryzen 3900X, 32GB RAM, Samsung SSD 970 EVO Plus 1TB) and when I check Process Hacker, I see that Edge isn’t using 100% of CPU, but still is frozen. I noticed that when it’s frozen, there are around 200 disk writes, fast changing, 9MB/s total:C:UsersmeAppDataLocalMicrosoftEdgeUser DataDefaultSync DataLevelDB256443.ldb … ( edge_workspace_disk.xls )When LevelDB writes stop, Edge is unfrozen.I’ve given msedge.exe processes high priority, but it doesn’t solve anything.I noticed this on previous versions starting from 122. I use Stable and Beta (to have two separate profiles) on PC and laptop. I waited hoping it will be solved, but nothing changed. It’s possible that developers only tested Workspaces with a limited number of tabs and not with power users like myself, who manage 10 workspaces with 200-600 tabs in each. The consistent unreliability suggests there may be unresolved bugs present in each version.I examined the LOG.old file in the Sync Data>LevelDB folders of each browser and noticed that when a freeze occurs, there is a specific behavior logged:2024/06/12-13:14:19.485 1a570 Generated table #365187@0: 40283 keys, 2109396 bytes2024/06/12-13:14:19.485 1a570 Compacted 8@0 + 1@1 files => 2109396 bytes2024/06/12-13:14:19.488 1a570 compacted to: files[ 4 6 7 0 0 0 0 ]2024/06/12-13:14:19.489 1a570 Delete type=2 #3651712024/06/12-13:14:19.489 1a570 Delete type=2 #3651722024/06/12-13:14:19.489 1a570 Delete type=2 #3651742024/06/12-13:14:19.489 1a570 Delete type=2 #3651762024/06/12-13:14:19.489 1a570 Delete type=2 #3651782024/06/12-13:14:19.489 1a570 Delete type=2 #3651802024/06/12-13:14:19.489 1a570 Delete type=2 #3651822024/06/12-13:14:19.489 1a570 Delete type=2 #3651842024/06/12-13:14:19.489 1a570 Delete type=2 #3651862024/06/12-13:14:19.491 179a0 Level-0 table #365197: started2024/06/12-13:14:19.492 1a0a0 Current memtable full; waiting…2024/06/12-13:14:19.500 179a0 Level-0 table #365197: 467718 bytes OK2024/06/12-13:14:19.503 179a0 Delete type=0 #3651942024/06/12-13:14:19.504 1a570 Level-0 table #365199: started2024/06/12-13:14:19.505 1a0a0 Current memtable full; waiting…2024/06/12-13:14:19.511 1a570 Level-0 table #365199: 467718 bytes OK2024/06/12-13:14:19.514 1a570 Delete type=0 #3651962024/06/12-13:14:19.515 179a0 Level-0 table #365201: started2024/06/12-13:14:19.516 1a0a0 Current memtable full; waiting…2024/06/12-13:14:19.524 179a0 Level-0 table #365201: 467718 bytes OK2024/06/12-13:14:19.530 179a0 Delete type=0 #3651982024/06/12-13:14:19.530 1a570 Level-0 table #365203: started2024/06/12-13:14:19.531 1a0a0 Current memtable full; waiting…2024/06/12-13:14:19.539 1a570 Level-0 table #365203: 467718 bytes OK2024/06/12-13:14:19.542 1a570 Delete type=0 #3652002024/06/12-13:14:19.542 179a0 Compacting 8@0 + 1@1 files2024/06/12-13:14:19.556 179a0 Level-0 table #365206: started2024/06/12-13:14:19.564 179a0 Level-0 table #365206: 467718 bytes OK2024/06/12-13:14:19.568 179a0 Delete type=0 #3652022024/06/12-13:14:19.572 179a0 Level-0 table #365208: started2024/06/12-13:14:19.581 179a0 Level-0 table #365208: 467718 bytes OK2024/06/12-13:14:19.584 179a0 Delete type=0 #3652052024/06/12-13:14:19.588 179a0 Level-0 table #365210: started2024/06/12-13:14:19.596 179a0 Level-0 table #365210: 467718 bytes OK2024/06/12-13:14:19.600 179a0 Delete type=0 #3652072024/06/12-13:14:19.604 179a0 Level-0 table #365212: started2024/06/12-13:14:19.611 179a0 Level-0 table #365212: 467718 bytes OK2024/06/12-13:14:19.615 179a0 Delete type=0 #3652092024/06/12-13:14:19.620 1a0a0 Too many L0 files; waiting… Read More