Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Echo of typing in posts is *very* slow.

Post

Echo of typing in posts is *very* slow.

+1
−0

I was just writing an answer on the EE site, and what was shown in the edit window (not even the preview) was way behind my typing. This made it very tedious, to the point of being unusable. I was going to write more, but gave up.

In one case I timed it, and it took 5 seconds for what I typed to show up. I also noticed that the fan on my laptop was running fast, so something was eating lots of processor cycles.

It's not doing it here right now, so that may mean it's site-dependent. Something changed within the last day on the EE site that makes writing posts nearly impossible, although it's fine here.

Response to comments

It's unlikely that anything changed within the last day, as we haven't touched the code at all in the last three days or so

Hmm. I've been using Edge on the same Win10 laptop all along. I suppose Microsoft could have updated something on me. (I hate how they do that, and you can't shut it off)

Were you using MathJax?

No. Also the delay was right in the edit window itself. The preview was probably delayed too, but a few seconds there doesn't really matter.

The post I was typing was this answer. It does contain an image, but the slow echoing of characters started from the beginning, before I added the image. It is interesting to note that some people can't see the image. I can see it with Edge and IE, but Firefox users apparently can't. Maybe that's a clue.

Response 2

you mean that when you pressed a key it didn't appear in the text box itself?

Exactly. I'm not talking about the preview below the edit box. I would type and see nothing for a few seconds, then suddenly the last half line of text I typed appeared, then this would repeat.

I wasn't even looking at the preview. Perhaps I should have to help diagnose this, but at the time I didn't think of that. In fact, I deliberately scrolled the browser window so that the preview was hidden. It's rather distracting the way it jumps up and down since that "Draft saved" stuff was implemented.

Can you try the exact same thing in Chrome or Firefox?

I just checked, and I have neither of those installed on this machine. I realize IE is old (although it works fine with most web sites), but Edge is a current and supported browser. You can't just tell people that the site doesn't work with the browser that came with their computer.

Added 3

I went to the answer where I originally had the problem, to see if I could get more detail on the symptoms. However, now the problem is gone. WTF?

I'm using the same browser on the same laptop as this morning. I can't think of what is different. The only other program that I directly ran on the machine in either case was a CMD.EXE shell window that was just sitting at a prompt.

I'll report here if I run across this bizarre symptom again in the future. Let me know if there is anything in particular you want me to try or look at if it happens again.

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (7 comments)
General comments
ArtOfCode‭ wrote almost 4 years ago

It's unlikely that anything changed within the last day, as we haven't touched the code at all in the last three days or so - there's a version number and date stamp for the current running version in the footer. Were you using MathJax? There's a deliberate delay (1s?) in that rendering to avoid it attempting to render on every key press and locking things up, and complex MathJax may itself take a few seconds to render. The non-MathJax'd post body should show up pretty quickly, though.

Olin Lathrop‭ wrote almost 4 years ago

@Art: See addition to question.

ArtOfCode‭ wrote almost 4 years ago

Hold up, you mean that when you pressed a key it didn't appear in the text box itself? We're not talking about the Markdown preview underneath it here?

manassehkatz‭ wrote almost 4 years ago

I know this sounds like a geek-hates-Microsoft answer, but seriously: Can you try the exact same thing in Chrome or Firefox? We have had some other reports of other issues, and that is my standard answer (I do this for a living, really) when my customers tell me something doesn't work in IE or Edge. Microsoft's browsers are a lot better than they used to be (competitive pressure works wonders) but there are still issues.

ArtOfCode‭ wrote almost 4 years ago

I'm almost certain that this is down to whatever your computer was doing at that time. Like the file input, text input fields are something I have comparatively little control over - certainly there's no code that would cause anything remotely like this to happen. So, rather than the correlation being "text takes a long time to show therefore excess CPU usage must be a symptom", I suspect it's actually "excess CPU usage is causing system slowdown including slow text input".

manassehkatz‭ wrote almost 4 years ago

Worth testing (if I get a chance, I'll test it myself, like I did with the image problem) in multiple browsers. I have found each browser handles different things faster - I have one customer where their major application mostly works fastest, by far, in Chrome, but one piece works fastest, by far, in Firefox.

manassehkatz‭ wrote almost 4 years ago

You can't just tell people that the site doesn't work with the browser that came with their computer. Well, you can. It just isn't recommended for a general-public site. I have done that for customer-specific (e.g., internal systems, even if accessed over the public internet) stuff.