Re: Bookmarks do not display in sidebar

On 10/11/16 09:55 AM, Peter Brown wrote:
> Hi All
>
> Peter Brown wrote:
>> Hi All
>>
>> I think I am running the latest - and sorry to say it but definitely not
>> the greatest - Seamonkey for OS/2: Mozilla/5.0 (OS/2; Warp 4.5; rv:38.0)
>> Gecko/20100101 Firefox/38.0 SeaMonkey/2.35
>>
>> A few minutes ago I clicked a link on a webpage and Seamonkey hung the
>> system.
>>
>> After restarting system and Seamonkey I find my Bookmarks are missing
>> from the sidebar. I closed the sidebar and reopened it - still missing.
>> I closed the sidebar and Seamoney; restarted Seamonkey and opened the
>> sidebar - still missing.
>>
>> I opened the Bookmarks Manager - no bookmarks.
>>
>> I should mention that *all* bookmarks are visible and work when simply
>> scrolling down the list from the Bookmarks menu item.
>>
>> So, the bookmarks are not missing they simply no longer appear in the
>> Sidebar or Bookmarks Manager windows. How do I rectify this?
>>
>>
>> Regards
>>
>> Pete
>>
>>
>
>
> This problem has resurfaced due to Seamonkey hanging again for no
> obvious reason - I was not even trying to play a video. It leads me on
> to 2 questions:
>
> 1] Does anyone have this build running in a stable manner?

It has been very stable here as long as I reboot regularly, perhaps 
every second day, otherwise it'll trap or freeze the system. Firefox has 
the same issue, probably due to fragmented shared memory. This is a big 
problem on Windows 32bit as well though it just crashes the browser

>
> 2] Why can I use Bookmarks available from the dropdown menu but
> Bookmarks Manager and the Sidebar both fail to load those same
> bookmarks? As Bookmarks are available from the dropdown menu it seems to
> indicate there is nothing wrong with the bookmarks file.
>

I'd guess places.sqlite corruption. Our port is currently somewhat 
broken with sqlite files not being finalized on closure and possibly 
other problems with them. I did open an issue at bitwise's github page 
as the issue affects Firefox as well. You can tell because the wal 
(write after log) files are still there after shutdown.
I've had success fixing issues in places.sqlite by opening an older SM 
and then closing it, by older I mean SM 2.21 or older. I was actually 
using 2.5 because it was handy (watch out for the webfont crash)
Dave