search

benweet / stackedit

In-browser Markdown editor
https://stackedit.io/
Apache License 2.0
21.69k stars 2.72k forks source link

Freezes/Crashes Browser Chromium on Android #1781

Open Emnolope opened 2 years ago

Emnolope commented 2 years ago

I am using Brave browser 1.35.103 Chromium 98.0.4758. 102 Android 8 Whenever I try to edit bigish files (1000 lines of English sentences) on StackEdit, the browser would get REALLY SLOW, and then crashes. The blinky cursor still blinks, and the clock still spins, and it's still responsive, but the lag time is about 15-40 seconds, it heats up the phone, it overloads the browser, and Android eventually force shuts the browser down.

Emnolope commented 2 years ago

This issue only presents itself with text files that contain maybe more than 200 lines of text. Whenever I start off a new file, with only two lines, everything's hunkydory, but the second I start to grow it, CRASH.

more details

Emnolope commented 2 years ago

These issues only manifested around Jan 29 2020ish. Sorry for reporting so late, I thought a bigger stronger developer would've fixed by now. So, I think the bug was introduced between Jan 15-Jan30.

Emnolope commented 2 years ago

I also tested the issue on regular Chrome on android, and I got the same issue.

Emnolope commented 2 years ago

This issue does not present itself on Firefox on Android though, however other issues are present which I don't want to talk about here.

Emnolope commented 2 years ago

So, the reason I actually made a post here is that I finally got a clue! So... I was editing a small document in Firefox, but I was sick of the bugs so I decided to move to a Chromium browser. I switched and it was great (small document) but I accidentally tapped on one of my behemoth documents, and my browser started to die. I was going to need to go back to the original (small) document. So I started rapid fire- closing the browser, starting the browser, and clicking the folder button, (This usually works after 50 or so tries) The idea is if the top bar loads before the document does, I can still reach the menu, before the website tries to parse the text and crash (I think). In that short time I can click on a smaller, non-catastrophic document. I was impatient though, so I decided to go to delete the contents of the large document on Firefox, so it wouldn't load much and burden Chromium. So I deleted the behemoth's text converting into smallhemoth, and HERE'S WHERE IT GETS GOOD. The deleted text still was present on the Chromium side, even after multiple restarts. So I think this is a cache issue.