Forum Discussion
Edge Workspaces sync BUGS
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...
After month of troubleshooting and 0 help from Edge developers here are my findings:
Regarding #1 bug nothing changed and I can't do anything. Workspaces have to understand that there are 200 then JAVASCRIPT redirect from Facebook and Instagram (maybe other sites too).
Regarding #4 bug with problems to access your workspaces you have to close your account and create new one, sorry. Problem is on Microsoft servers. Sometimes you might access your workspaces from other browser or computer but it is random and you will loose access eventually. If you have this in your edge://workspaces-internals :
Spaces Event: EdgeFluidCSPStorageHelper failed at OnGetContainerListComplete
{ "Date": "0", "ErrorCode": -102, "PrimaryError": 17, "SecondaryError": 37 }
Spaces Event: WorkspaceManager: Failed to initialize Fluid Error code:46 tag:-41
Spaces Event: Fluid Manager Process Failed
"Failed to initialize Fluid"
Just run! Microsoft won't help you and won't send you a backup. If you want to feel safe create new account and use Tab Session Manager that will save sessions everytime you close browser or window.
Regarding #3 bug I have no idea why Workspaces can stop sync without a notice. Sometimes it can stop sync, but there will be red dot.
And most important #4 bug:
It appers that Workspaces is poorly written and highly abuses Chromium sync (made for syncing bookmarks, settings, history, not for workspaces) with LevelDB in Sync Data folder. Opening any Workspace start up to 3000 I/O writes delta and 2000 I/O reads delta, writes to disk are also high making hundreds of gigabytes a day. It contributes to SSD wear! It doesn't freeze a system and there are resources left to run even another browser, but such I/Os make browser unresponsive. I'm sure it's because workspaces because I opened same set of tabs without workspaces and there was no problem and I also saw that when I disconnect form the Internet or block IPs connecting with Edge - it's unfrozen - workspaces can't sync and LevelDB writes go low. Workspaces make LevelDB tables with many keys and long values of favicons and updates fast. LevelDB can't keep up so it freezes the browser.
Can anyone except developers do something about it? Only idea I think is to move Sync Data folder to Ramdisk, I have to test it. If it fails then workspaces are just useless, full of bugs crap with no support.
I'm continuing to work on optimizing Workspaces on my side since I have not received a response from the developers and there are no changes in the new versions of Canary. Workspaces are useful but constantly freeze, making it unusable. If I cannot make it function smoothly, I will stop using it.
I installed ImDisk and created RAMdisk for 'Sync Data' folder. It moved I/O from SSD to RAM, it makes writes much faster and prevents from excessive wear Edge does to SSD. Unfortunately, it does not stop Workspaces from experiencing hours-long freezes.
I think there is a limit of CPU power allocated for one process. The main Edge process does not utilize full CPU power when necessary. On my two PCs, it utilizes either 12.5% or 4.1% of CPU power. This correlates with the number of threads on these PCs—12.5% for 8 threads and 4.1% for 24 threads. It appears that the main process is using only one thread (12.5*8=100%, 4.16*24=100%), although the process manager indicates it is using more than one. Is there a limit to CPU usage for a single process? Can I allocate more CPU to the main process to enhance its speed?
The screenshot from Process Hacker shows the CPU usage for the main process is flat, as if it was restricted in some manner. The CPU has 24 threads, suggesting it may have been limited to 1/24th of the CPU's capacity. However, it works across multiple threads.
