file attachments

comments

Thanks for the dump. I don't see PTVS anywhere in the module list or callstack, so it's unlikely that we're the cause.

This crash has been reported a few times (through Windows Error Reporting), so the VS team is aware of it and have dumps to work from already (buckets -385263974 and -382685050 for anyone internal who wants to look them up).

I'll close this out shortly, but I'm intrigued as to why we're not showing up in your module list if you've got a Python project open. Any idea? (You can open the minidump with VS to see the module list, then search for 'PythonTools'.)

Thanks. I'm not sure that PTVS is the cause however I don't get the crash if PTVS isn't installed however. I uninstalled and installed PTVS numerous times with different versions and it crashed every time when PTVS was installed and not once if it wasn't.

It looks like the problem has to do with the working directory value in one of the python projects. I was able to cut down the reproducible from 51 C++ projects and 9 python projects to just a single python project. I have attached this repro to this comment,
however you can also reproduce it with the following steps.

Create a new python application project (and solution)

Change the working directory in the python project to ..

Do a Find in Files search for some arbitrary string.

This repro fails for me on two machines, one with a clean VS2013 install with the Nov 8, 2013 PTVS Dev build.

Previously I was only running into this problem when I had a file open in the editor that contained multiple "dots" in a single portion of the name (e.g. a version like "1.2.3.4" but now I cannot use "Find in Files" at all
without crashing Visual Studio, apparently for the same reason as the OP, working directories for Python projects that contain relative pathnames starting with "..", which is an issue I cannot easily work around.

Yes, this is definitely a bug in VS2013 that we are somehow triggering. They have the crash reports and hopefully it will be fixed, though we'd still like to resolve it ourselves (since we can get a release out sooner). But PTVS is not the sole cause of
this issue, so we may not be able to fix it on our side.

It looks like they had the fix ready just too late for update 1. As far as I can tell (not having spoken to the people involved), I think the fix will be in Update 2. (There's a
CTP available if anyone wants to check, though be careful, since it is not production-ready and I'm not sure it can be uninstalled...)