New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The editor is being slow lately #289
Comments
What browser/os do you use? Have you tried on different browsers? |
I am using Chrome Version 32.0.1700.77 Macbook Pro OSX 10.8.5 Which other browser would you like me to try ? Henry On Sat, Jan 25, 2014 at 3:00 PM, Benoit Schweblin
|
Safari for instance. I have noticed some other bugs with Chrome 32 on OSX, but it's not particularly slow for me. Can you also try in Chrome to:
|
Can confirm. OSX 10.9.2, uptodate Chrome. After a while typing becomes extremely sluggish. It helps to quit and restart, but after a few more minutes of typing it's becoming nearly unusable again. |
Same. +1 |
Any pattern to reproduce that? Are you editing a huge document or do you have more than 100 local documents? |
If the problem occurs on a big document, you probably have to put paragraph titles to take advantage of partial rendering. See #177 |
The document is fairly small but I do have a lot of documents, yes. Other
|
Actually, it would be very helpful if you could send me a CPU profile (on https://stackedit-beta.herokuapp.com/ preferably). Basically, using Chrome:
You can send this file to my personal address (see my GitHub account page). Thanks. |
I've been using the version at https://stackedit.io/#, editing this medium-size blog post: http://flohofwoe.blogspot.de/2014/04/cmake-and-android-ndk.html I have recorded a profiling session on stackedit.io, but couldn't reproduce the slow-down during the session (sending this to your address right now) |
@benweet done, hope it helps |
Great I'll have a look when I get a chance. |
I've fixed some memory leaks in event handlers that could lead to performance degradation when switching documents many times. Not sure it solves your problem though. Let me know if it's better. |
+1. I actually attempted to use the beta just to check fi the performance degrades there as well, but I was unable to see the existing docs there (probably using a different local storage) and then hit a rendering issue. I'll try to give it a closer look and report. |
You can export/import documents from one platform to another using Settings>Utils. |
@benweet sorry nope, still the same. Want another profile? |
@Swader Sure. A heap snapshot would be helpful as well if it's not too big (normally it's 25MB with a few documents) Thank you in advance. |
@Swader I'm just thinking, the heap snapshot will contain some parts of your documents. So you probably don't want to send it to me... |
I don't really care about that, there's nothing sensitive. I'll try and get Bruno Škvorc Web Developer; PHP Editor - Sitepoint.comwww.bitfalls.com On Thu, Apr 24, 2014 at 8:52 PM, Benoit Schweblin
|
@Swader, I've push some performance enhancements in version 3.99.6 (beta). Can you tell me if it's better? |
I just tried the version at https://stackedit-beta.herokuapp.com for a new blog post, and the slow-down after typing for more then half and hour is still there. I tried changing some options (like lazy-rendering off) and initially it was fast again, but then slowed down again. This time I recorded a CPU profile in Chrome (with lazy-rendering off though, but this didn't seem to make a big difference). I'm sending it to your gmail-address right now... |
Fixed in 3.99.7. I managed to reproduce the problem by running some stress tests. It was a tricky one. |
Yay, it's fast again :) Thanks for fixing this! |
Hey guys, I am experiencing the slowdown again. |
Slow for me when directly using it with Google Drive files. Chrome 57.0.2987.98 (64-bit). on Mac OS X. Also tried with Safari, slow for me too. |
Starting a few days ago, the editor has been slow and not responsive to what I am typing. It would sometimes take a few seconds before it catches up, and the screen would pause for a short second or two before you can type or move the cursor around again.
The text was updated successfully, but these errors were encountered: