On Sun, Dec 25, 2016, at 11:15, moos...@gmail.com wrote: > cat(1)ing https://www.cl.cam.ac.uk/~mgk25/ucs/full-bmp.txt leads to a > segfault inside Xft (with 50% chance) furthermore my attempts to > reproduce it under valgrind(1) failed.
I am using the latest st (git pull) with no changes to config (cp -piv config.def.h config.h). I don't know about Xft, but when I cat that file, it takes a long time and makes st very very slow. According to htop, st uses about 100% of a core while it cats. Even after it is done catting, st is very slow. It takes 3 to 6 seconds for my shell prompt to display again when I just hit enter (I've tried with both fish and mksh). Using the reset command returns it to normal speed. Is this a bug? I just tried with xterm and there is no slowdown.
