link-map

link-map copied to clipboard

Thank you for submitting an issue for Link Map. To help us better understand your feedback, please fill out the following template(If you think it's too complicated, just write down whatever you want):

Description

Link-Map is not saving all the tabs compared to Google Chrome and Tabs Outliner

Steps to reproduce (if applicable)

kill all the chrome.exe process

Expected behavior

It will save all tabs at the time of crash

Actual behavior

It seems like it only shows 76 tabs compared to Tabs Outliner which shows 79 and Google Chrome when restoring tabs for not shutting down correctly is also at 79 tabs.

Screenshots (if applicable)

[Include screenshots or images to help clarify the issue, if applicable.]

Additional information

[Include any additional information that may be helpful in resolving the issue.]

Thank you for your feedback.

Hi @Almighty188, Thanks for your report. This is indeed a problem. Could you please tell me, when you kill the process of chrom.exe, the Link Map is open or closed?

For the current version, when the Link Map Window is closed, it wouldn't record windows/tabs in the background.

And no matter what the cases above, I will add the feature that making Link Map record Tabs/Windows in the background, with higher priority.

I am not 100% certain but I can always try this again in the future if you can let me know how I can clone the current window tree intto a suspended tree to recover to just in case since at that time, I was still panicing about the following issue which was how I discovered Link-Map, do you know if i's possible to manually see what was on the suspended windows as you are more familiar with how Link-Map and Tabs Outliner works.

https://github.com/GarinZ/link-map/discussions/48

@Almighty188

1. About clone feature in Link Map For now in Link Map, there is no such feature that cloning a subtree(e.g. window tree) yet. But this feature is in schedule to be added in later update.

2. About manually see what was on the suspended windows:

I'm not sure I have understood correctly. Here are some methods I could give according my current understanding:

• Method1: Most convenient way, which you could already know, is import data.
  • For TabsOutliner: Settings - Export Tree to File
  • For Link Map: Setting - Export Link Map Data
• Method2: Checkout the indexedDB
  • open dev tools in Tabs Outliner/Link Map Page -> Copy the value in indexedDB

@GarinZ

Maybe that is why I couldn't find how to create a identical tree that is suspended so I can open it should the test fail for whatever reason. What file in the IndexDB is the tree actually stored in? I know there is the *.blob folder but all it has are folders which have no files in them. Then in the *.leveldb folder, there are files that are *.ldb, *.log, CURRENT, LOCK, LOG, LOG.old, LOG# where # is some number and then a MANIFEST file. What happened in my case was I had TabsOutliner working fine, Google Chrome Beta had a new update so I restarted Google Chrome Beta as prompted except the entire tree in TabsOutliner was gone and basically I managed to get back the windows that were working when I did the ctrl-shift-T but lost everything else which I had suspended in the tree and used like bookmarks so I am trying to see if there is a way I can extract the data manually.

@Almighty188 Sorry for the slow response , I went to somewhere without my Laptop these days. And don't worry, I will help you. I'm trying to find a way to parse these files. I think if you still have these raw data of indexedDB, we could recovery your links. I have found a opensourced go lib in Github called idb-parser today, and in my current progress, this lib could parse data from .idb files. I still need to do some rewrite work to make it having the ability to recovery TabsOutliner's data.

But I think we still have a hope, is it? If I have any new progress, I would inform you in this issue.

Many thanks @GarinZ for your help. Take your time as I am sure it's going to be a interesting experience whether good or bad. I guess Google can hold everyone's data hostage and also lose everyone's data at the same time.