150 and 150.1 very unstable

[cumulativedelta]

almost ready to uninstall 150 and re-install 149... 150 corrupted my initial profile... tried everything to stop the program from turning into non-stop CPU hashing... copied the profile, deleted suspect profile files and folders, uninstalled and re-installed v150 and finally without thinking "refreshed" - that created an hour of work rebuilding my setup and i thought it was good to go... nope
     with all that done i re-loaded my windows and tabs (thank God for Tab Session Manager)... and an odd thing began happening, after a close and a timely process shutdown and re-open the program would open the tabs and windows from a previous session with all the favicons showing on the tabs i had visited, then all of a sudden a duplicate set of windows would open and the originals would close and now none of the tabs i visited had the icons on them any longer, just the text... geeze, what next... found that if i copied the profile i got a stable profile where the tab icons would persist between exiting/restarting but now it's back to this persistent hashing of the CPU and in-ordinate memory usage and hung tabs that were previously loaded fine... And best of all it's back to hanging every single running process after i exit and won't throw a crash box anymore and i have to go to details because the processes aren't available in the "processes" tab any more but only show in the "details" tab so i can force exit and shut down the program...   Forgot to mention i had turned off Bitdefender's browsing defense utilities yesterday before i uninstalled/re-installed... Can't tell if there's actually an extension like AdBlocker that is actually causing the "cpu hashing" because it does it with extensions all turned off.... just load enough tabs and presto-chango Hashing Monster (75% core usage on the allotted cores)

what is so insecure about v149 that i shouldn't use it ?

[cumulativedelta]

just noticed now that the tabs on the menu bar for extensions don't work even though the extension is loaded and "running"...  most of all can't shut down cleanly using File Exit... processor hashing begins at shutdown... history is set to "remember" i've heard that can delay a clean shutdown...

oh, and the other thing - i use a startup file to restrict programs to physical cores on the processor and have used this on FireFox for years with no problems... the program now ignores processor affinity and runs on all cores - this just started today with v150.1

[cumulativedelta]

and now can't even launch FireFox without it going directly into CPU hashing and of course it won't shut down successfully as all the processes just keep running and running and running and running and running....

you folks really screwed up a good thing...

[cumulativedelta]

Just discovered that if continually delete the temporary cached files and pages it runs in a more stable fashion

[cumulativedelta]

well, just thought that might have helped... it didn't over the long run... the program still "locks up" and begins the 75% usage hashing on its allotted cores and the processes won't quit on their own, still running on the details page of Task Manager but not on the processes page... waiting for 150.0.2

[cumulativedelta]

well, figured it out... after how many days... LOL    bsides it's hard to talk in an empty room