Help understanding some bad emacs behavior

[Austin Bingham]

I'm working on some code-completion related packages (company + ycmd), and something I'm doing is triggering some pathological behavior that I could use help on. Under some conditions that I haven't fully characterized yet, a thread in emacs goes off on an extended, recursive-looking adventure of some sort. What I'm hoping is that someone on this list can look at the attached stack info and give me some hint as to what might be going on.

My assumption is that some of my elisp code is just doing something wrong, but I don't know what. Does this stack info give anyone any clues as to where I might start to look?

Austin

emacs_sample_completion_loop.txt
Description: Text document