Slow performance

[PMassicotte]

Hi.

When I am typing a message, the CPU usage goes up to 100% and the typing is very slow (basically unusable).

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 60
Stepping: 3
CPU MHz: 2004.890
BogoMIPS: 7183.07
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 8192K
NUMA node0 CPU(s): 0-7

[PMassicotte]

I noticed that if I remove my signature the problem is resolved. So it is kinda related to a (simple) html signature that I am using.

[bengotow]

Whoa! That's super interesting. If it's not too personal, could you post a text file with your signature in it? You could remove / replace your info. I think there may be something specific about your signature that is causing one of our processing steps to hang.

[PMassicotte]

There you go. The signature was written in markdown and then html generated in Atom. I just noticed that there is a TON of unnecessary html code. This must be the problem.

signature.zip

[molstrangler]

I had the same issue when using my own HTML signatures. when replying to an email, entering text was painfully slow. I revert to standard N1 signatures and performance has returned.

[grinich]

@PMassicotte what language is your OS set in? Could this be a dupe of #1069 ?

[PMassicotte]

I am using Linux Mint (English language). Not sure if it is related to #1069 since it was occuring all the time, not only when replying.

[jacobwindsor]

I also notice the same issue one Windows 10. Most definitely to do with the signature since performance is normal when I use an account with no signature.

UPDATE:

I don't believe this happened until a recent update although cannot confirm that 100%.

[jackiehluo]

Another incidence: https://twitter.com/vinnytroia/status/748373119119859712

[jstejada]

Another incidence: https://nylas.zendesk.com/agent/tickets/4031

[emorikawa]

It appears to be related to this issue: #1069 I'm closing this to merge it into #1069