Tabs Outliner window freezes repeatedly

[rmk...@gmail.com]

I lost my TO tree Friday and recovered it using the directions in your video linked in this answer:
https://groups.google.com/forum/#!topic/tabs-outliner-support-group/sao3WTioNAI

And everything worked great until Saturday night. I think the recovery of my tree is unrelated to my problem, but I mention it just in case it makes a difference.

Saturday night, a PDF download seemed to freeze Chrome. I can't remember now if it was all of Chrome or just TO that froze at that time, but I did a force-quit on Chrome and restarted it.

TO responded properly, but now it periodically freezes again. I can't tell if something I'm doing is causing the freeze or if it just happens. I'm not downloading any more stuff at this time. I think it has frozen four or five times since Saturday night.

I uninstalled TO and shut down Chrome, then reinstalled it, but that didn't help.

I'm running Windows 7 professional, Chrome is Version 38.0.2125.104 m, and TO is version 0.4.81.

Right now my console says :
=== TabsOutliner Background script code started === background.js:91
IDB READ-DONE TabsOutlinerDB34 background.js:61
No valid v34 data in database, or with unknown lastSaveTime (V34DataSaveTime, localStorage.lastSessionSnapshotSaveTime): 1413724183424 1413728970627 background.js:66
- Files ------------------------------- background.js:77
h-backup-1413723492278-5.json background.js:77
d-backup-1413723491636-5.json background.js:77
currentSessionSnapshot.json background.js:77
IDB, file, localstorage snapshots timestamps & lastSessionSnapshotSaveTime: 1413724183424 1413724183424 1413728970627 1413728970627 background.js:66
Data in localStorage have known lastSaveTime, will restore tree from localStorage

...while I was typing this post, it froze, and now the console log window is completely empty.

[Vladyslav Volovyk]

> periodically freezes again

Does it unfreeze after some time after this, or you need to kill the Chrome or Tabs Outliner process?

[rmk...@gmail.com]

It does not seem to unfreeze - I think the longest I've waited is about 10 minutes. I do get the "unresponsive window" warning from Chrome, so it's pretty far gone. When I kill it from that prompt and click on the "click here to restart the extension" it reopens the window but won't run properly.

Chrome keeps working through this but I miss Tabs Outliner and I want it back, so I exit Chrome. One process hangs on after the exit and if I don't kill that process, Tabs Outliner still won't restart when I restart Chrome.

I can exit Chrome normally, kill that process and restart Chrome, and Tabs Outliner will work for about 10 minutes, then freezes again.

Something else I noticed: shortly before TO freezes, all of Chrome stops working right for the Save As command, so I can tell that TO is about to stop working.

[rmk...@gmail.com]

I replied - did I do it wrong so you didn't see, or perhaps you're just busy?

[rmk...@gmail.com]

Ignore my post yesterday, I am being unreasonably impatient. Your work is so useful, I'm missing it, but that doesn't give me an excuse. I'm sorry for posting it.

[dragon788]

I've noticed that the PDF and Flash plugins are becoming less stable in the newer versions of Chrome as Google is removing the NPAPI. Have you tried disabling or closing any tabs that might be trying to open these types of files?

[rmk...@gmail.com]

I'll investigate that, thanks!

More detailed answer - I don't have any tabs currently open that include PDFs, though I might have one closed in the tree. I'm assuming that won't cause the problem you mention.

Flash, though...I'm not even sure I know how to recognize which pages are doing flash stuff and which aren't anymore. Hence the need for deeper investigation.

I'm sort of sitting on the problem, hoping Mr. Volovyk will have time to make a suggestion soon, but as I watch the behavior I'm beginning to seriously think the issue is with Chrome, not with Tabs Outliner. TO is just the canary in the coalmine, the part that I can see keel over and fail while Chrome is suffering from an otherwise invisible issue. Even if I disable TO in the extensions pane, save-as stops working on Chrome after it's been running a while. That sounds like it really isn't TO at all. My next step then, is to read up on what you do when Chrome in general is misbehaving.

Thanks for pointing to a possible cause!

[rmk...@gmail.com]

Mr. Volovyk very kindly contacted me about my problem, and suggested that he felt it was a Chrome profile problem, that my profile got corrupted during the last Chrome update.

I needed to back up my Tabs Outliner tree to HTML so I could transfer it to the new profile, since it is not saved by Chrome sync.

At first I tried Chrome's internal setting to create a new profile, but that didn't work. Then I uninstalled Chrome and reinstalled, and that didn't work. It wasn't until I uninstalled Chrome, restarted my computer, and then reinstalled Chrome that I seemed to get good results.

Chrome has been running for several hours now without the freezes I was seeing, and I believe the problem is solved.