Issues observed in 5.2.1

Developers
#1

Folks,

Windows 11 64bit, Tiddlywiki 5.2.1 Chrome Version 96.0.4664.93 (Official Build) (64-bit)

I am getting some serious errors; Here is what I am seeing;

  • On my wiki, or on download of tiddlywiki.com or fresh empty;
  • Exporting from advanced search filter more than one tiddler, or using export on a tiddler I get an “Awsnap” failure

Snag_bf33ff

However I (and you may) can reproduce this now in Chrome;

  • Download empty or the full tiddlywiki.com wiki and try and export a tiddler - bang “Awe snap”

This is not occurring on FireFox!

Anyone else having trouble drag/dropping on chromium?
#2

Tested on Chrome 96 Win 10, everything works just fine!

#3

I have the same issue as Tony on mobile – tested on Chrome (Android), version 96.0.4664.92: Chrome crashes (“Aw snap”) on attempting to export multiple (2) tiddlers using a filter from Advanced Search.

Tiddloid Lite version 1.2.1 works fine, but I think it’s based on Chromium (i.e. non-Google), so the way things work could be slightly different to Google’s “fork” of Chromium (i.e. Chrome).

#4

Starting to look as though the 5.2.+ branch is going to be littered with interim Chrome-FIX releases… the hell are Goolag doing???

:angry:

#5

For all intents and purposes, Google also “owns”, builds, develops and maintains Chromium as well. So if the changes they made are actually in the Chromium base, those changes will eventually catch up with all the Chromium based projects.

In this case, Tiddloid is months older, and so wouldn’t be experiencing anything yet. Usually you only need to update an Android app if you have new features or to accommodate changes in new Android versions.

#6

I think the exact build number is going to be useful here. Like some builds of vsn 96 work, but some don’t.

#7

Folks,

I hope this is not true, but I want to foreshadow there may be more problems with Chrome and/or TiddlyWiki 5.2.1 on windows. I have a Windows 11 machine and getting the aforementioned problems, but also unsolicited blue screen of death reboots ONLY so far while using tiddlywiki in Chrome, but not with FireFox.

I will continue to analyse the combinations, try it on Chrome canary etc… and provide feedback here until I have something worthy of a GitHub submission. Please see if you can reproduce these.

#8

I will say, that while my use of Tiddlywiki has been limited since I upgraded, I have seen none of the issues spoken of. I am using Windows 11 and the latest build of Chrome version 96.

1 Like
#9

Are you running any anti-virus software?

#10

Only virus which Microsoft installed with Windows 11.

#11

Is it possible to turn it off for a test?

#12

Mark

Thanks for your suggestion, i will in the fullness of time, after your comment i thought it worth trying however searching for window BSODS I found a reference to intel and found a firmware update. My use of tw5.2.1 coinsides with my move to a new pc an 11th gen i7 NUC. There is also a suggestion of a problem with win 11 and some recent vidio issues, so i will look at chromes use of hardware acceleration.

I am reassured no one else is reporting the same issues as per @HistoryBuff.

i’d rather be a victum than find a systematic problem that makes others also victims.

Thanks for the help. I will report back if tiddlywiki or the Timimi saver is further implicated.

#13

I can confirm that my BSODs are fixed and appear unrelated to TiddlyWiki

However in Chrome I can cause a tiddlywiki to fail in Chrome simply by trying to export a tiddler to JSON. In many of my wikis, but not all, I get the Aw snap.

Error code: RESULT_CODE_KILLED_BAD_MESSAGE

I am going through these wikis to see if there is a common denominator and I have not found it.

#14

Thank you for going through all those steps. I haven’t upgraded to Windows 11 yet and I use Chrome as my primary browser.

#15

Have you tried the same TW’s without your AV running, or on another machine with no AV? Since you say it happens with empty files, possibly you could share the file?

#16

FYI, I just exported a tiddler to a JSON file with no issues. I wish I could be of more help other than to say it’s not a widespread issue.

1 Like