tedit development and design discussion
-
-
@danfro Thanks ! No crash (currently) with the artifact. However, with the latest official built, I cleared the cache, and I didn't get any crashes after that too.
-
@domubpkm Thanks for testing. Yes, clearing the cache did help before too. I assume when I build the app with clickable, this clears the cache as well. No idea why something in the cache can make the app crash though...
-
@danfro Installed from artifacts, cleared the cache again, app still crashes.
-
@danfro I don't know anything about it, but couldn't it have something to do with the size of Tedit's cache?
-
@messayisto Same here: Deleting cache + config + data does not help.
-
@domubpkm App cache is handled automatically. I don't think there is anything I can do about the size, except maybe clear cache every time tedit is closed.
-
@stanwood and @messayisto very strange. Just to be safe, did you also try a reboot?
Could you please check the apps log and see if there is anything in it? All I see is an error about a binding llp in TextInputPopover. But that is also when not crashing, so likely not related.
Hard to track down if not reproducible. But a very annoying bug...
-
@danfro said in tedit development and design discussion:
maybe clear cache every time tedit is closed.
Why not if it's possible and even if it may not be the whole reason for the bug.
That said everything is ok for me (for now...). -
@danfro So I shut the device down during the night as I used to, and started up this morning. No change.
Don't know where to find the logs (I'm not keen on installing apps such as "Log Viewer", which can lead to system instabilities). -
Lionel did already create a fix for gitlab
Thanks for this !! @lduboeuf . Really needed currently.
-
@danfro https://dpaste.com/ATTBQZVFR
hope that helps -
@messayisto Thanks a lot. Although sadly this doesn't help much. The only error is the "binding loop" one, which I get also without crashes. So not related I assume.
-
@stanwood Logs can be pulled via
journalctl
. To grab the logs for tedit, you can run in terminaljournalctl --user -u lomiri-app-launch--application-click--tedit.danfro_tedit_3.4.0--.service >>tedit.log