How can we help you today? How can we help you today?
bug_rodeo_clown

Activity overview

Latest activity by bug_rodeo_clown

Remaining Tab History -> SQL History issues (as of 10.13.7)
The Tab History -> SQL History migration has been bumpy, the 10.12.5+ releases were unusable (10+ second searches, crashed when typing search query too fast)I reverted to 10.12.4 for a while before...
1 follower 1 comment 0 votes
Hello,  I spent some time trying to debug this issue in 10.12.6 (thinking it was an issue with my system), and have just found this thread (revealing it's a sql prompt bug) In my case, the Tab History window takes ~20 seconds to return results, at first opening, and after every single search character is entered. (seems like it's trying to issue a new query each character). If a character is entered while it's already searching. (ie typing a letter before the 20 seconds, or typing 2 in a row) it crashes with that semaphore timeout. While it's hanging for 20 seconds, the RedGate.SqlPrompt.SqlHistory.Server.exe chews a cpu core for the whole 20 seconds. Running xperf on that process while it hangs shows nearly all the time is spent in mscorlib.ni.dll!System.IO.Path.GetTempPath(), notably spending most of its time in in System.IO.LongPathHelper.TryExpandShortFileName(). Running procmon while it hangs shows it reading directory properties on my appdata/local temp directory > 18,000 times, taking ~1ms per loop iteration (call -> call latency). I notice it calling against my profile directory 8.3 shortname. [image] Note: My temp directory is nearly empty, maybe a dozen files currently in use. I hope this is useful. If you have a public debug symbol server, please let me know. / comments
Hello, I spent some time trying to debug this issue in 10.12.6 (thinking it was an issue with my system), and have just found this thread (revealing it's a sql prompt bug)In my case, the Tab Histor...
0 votes