Crashing here as well!

Slimjet bug reports
Kewpycat
Posts: 35
Joined: Mon Jan 14, 2019 1:38 pm

Crashing here as well!

Post by Kewpycat »

Crashing all the time. Started Saturday morning Oct. 26.

User avatar
W0gh1tyr
Posts: 8
Joined: Wed Apr 06, 2022 10:47 am

Re: Crashing here as well!

Post by W0gh1tyr »

Same here. I downgrade to 42.0.3.0, and appears normalized
Windows 11 - Slimjet - 40.0.2.0 - 64 bit - Brazil

Kewpycat
Posts: 35
Joined: Mon Jan 14, 2019 1:38 pm

Re: Crashing here as well-But ONLY on "log in" screens.

Post by Kewpycat »

Not sure if anyone else mentioned this, but it dawned on me that the ONLY time it crashes is when I attempt to enter "Log in" credentials.

I can use Slimjet (Ver. 44) all day without it crashing if I avoid having to log into a site. As soon as I click on to a field to input either a user name or password, or if my password manager (RoboForm) enters the credentials for me, THEN it crashes. But if I just surf around various sites without having to enter a username or password, it works just fine. It even works on sites that I'm already logged into without crashing.

Anyone else experiencing this?

Kewpycat
Posts: 35
Joined: Mon Jan 14, 2019 1:38 pm

Re: Crashing-FIXED with latest updated version

Post by Kewpycat »

I just updated to Ver. 44.0.6 and it seems to have resolved the crashing. I was able to log into about 10 sites and all let me in without crashing.

Texstar.
Posts: 23
Joined: Sun Jan 18, 2015 6:36 am

Re: Crashing here as well!

Post by Texstar. »

44.0.6.0 crashes even more for me. I even started with a clean .config/slimjet folder.

Created TensorFlow Lite XNNPACK delegate for CPU.
Attempting to use a delegate that only supports static-sized tensors with a graph that has dynamic-sized tensors (tensor#180 is a dynamic-sized tensor).
[1026/231819.395410:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[1026/231819.395512:ERROR:elf_dynamic_array_reader.h(64)] tag not found
Trace/breakpoint trap

sweethoneybee
Posts: 20
Joined: Tue Feb 21, 2023 4:42 am

Re: Crashing here as well!

Post by sweethoneybee »

I have no more crashes with version 44.0.6.0 too. Strange thing is that the release notes say the reason was an update for Windows 11 (fix crash after windows 11 update) and i´m using Windows 10 from 2021 without any updates. :?
And it even gets more strange because also people who are using Linux reported that crashing problem and Slimjet for Linux didn´t get updatet. It´s still version 44.0.5.0. :?
And now it gets really exciting. Slimjet for Linux also has changed yesterday evening but the version number 44.0.5.0 was still retained. I downloaded this version a few days ago and could see this morning that the hash had changed. :?

Kewpycat
Posts: 35
Joined: Mon Jan 14, 2019 1:38 pm

Re: Crashing here as well!

Post by Kewpycat »

I too am on Win 10 and I checked my update history, the last update was on Oct. 15, so I'm not sure what a Win 11 update had to do with it, at least on my system.

Nonetheless, 12 hours later I'm still stable after updating Slimjet to Ver. 44.0.6; I just visited about a dozen sites that required a log on, and not a single crash.

User avatar
oftentired
Posts: 1769
Joined: Tue May 13, 2014 3:14 am

Re: Crashing here as well!

Post by oftentired »

44.0.6.0
fix crash after windows 11 update

Win 10 has similar updates to Win 11. He probably initially determined it from a Win 11 crash report and started working on it at that point.
For those of you who wear aluminum foil hats, the voices lie, don't believe them!
Mostly my replies are about Windows OS. If not I try to remember to specify Linux.

64 Bit SJ on Win 11

beer2beer
Posts: 1
Joined: Sun Oct 27, 2024 1:19 pm

Re: Crashing here as well!

Post by beer2beer »

44.0.6.0 crashes when selecting google search engine :shock:

sweethoneybee
Posts: 20
Joined: Tue Feb 21, 2023 4:42 am

Re: Crashing here as well!

Post by sweethoneybee »

oftentired wrote:
Sun Oct 27, 2024 9:56 am
44.0.6.0
fix crash after windows 11 update

Win 10 has similar updates to Win 11. He probably initially determined it from a Win 11 crash report and started working on it at that point.
That could make sense.

Post Reply