(I suppose a sea monkey Would have a heel, eh?)

Doze, not *nix version - on the 98SE drudgery box, otherwise ambling along nicely at 600 MHz. (Have also Ubuntu 7.0x with Sea Monkey - though see no reason to break it in similar fashion.)

Cause:
Seems that as one approaches, then passes 3M bookmark filesize:
first the dread periodic msvcrt.dll crashes of the Suite (all-along in Doze) go from not-at-all --> noticeable, then frequent. Finally, a next launch causes seppuku, within seconds. Spinners awaiting an open pipe Stop Spinning / kill process time.

Oh and.. it's apt to write garbage (in that trice) into the dread prefs.js file.. a not-nice distraction from the primary cause hunt. Prior builds, on hand - are no relief either - nor the latest V.112 SeaMonkey d/l'd via an ancient Netscape 4(!).
(Reducing likelihood of Billyware-rot, having perhaps contributed.)

Problem remaining:
While 'bookmarks.html' is described as 'just html' - I'm running out of lore for halving this monster (or even temporary reduction by 15% or so, so as to use the primitive editing within Navigator for a final solution.)

That is, while unloadable-as-'bookmarks':
the 3.218M file can be opened-as-file, within the browser (shakily) or in Composer.
In latter - I could copy some chunks to another instance, then delete orig.
But saving the salvaged bits via Composer, as a small test test file:
gets a rousing No Action on, 'Import' [this]. No error message either, just nada..

(I had recent prefs.js, b/marks on backup-CD natch, including regressively smaller ones - still, want it all - even if via next loading sequentially, on the occasional need for early 'data'.)


Any ideas? re Why.. SM should eschew my small file made by ITS utility -- when Import will cleanly re-import a dup of its default file?


WPB

Good point re 98.. probably only a Moz developer would have a handle on likeliest culprit. Then too - it's been years since I've seen a purely-OS crash needing 'reset', although the evident msvcrt incompatibility still leaves the culprits moot. Good idea to see if FF would be immune - seems also likelier that *nix would have no sissy too-tiny buffers everywhere; will give that a try, too.

(Somewhere, some time ago I read of a .dll version alleged to be superior to the default; turned out you had to d/l some 100+ MB of bugfixes for some VB-add-on! just to get *that* version from the Beast. Yashure..)

Given that there is a rudimentary file sys, I see that I need to grok how you extirpate sections (other than just a folder at a time), reassemble pieces after massaging. Peering at Source may suggest some redundancies best preserved along the way(?)
Or - hints in your linked utils may clear that up.

Thanks for the leads. Actually, much of the 'data' needs no saved (now obsolete) URL at all, so may be best just collected in a file, searched by keyword == no structuring! (Not even Info Select\ufffd)

Hadn't considered a home page, see the appeal - still, it's a bit late .. after it's all grown jus' like Topsy. I've counted on search to solve the random filing and now.. and Now - they want to force me to be Organized !?

WTF they think I Be - a CPA !?

Gracias