Problem

@Mayur!
Are you share this PDF file?
---------------------------

Hi,

Please be specific on your question.

some times i am getting this error "new instance of visual studio 2005"

Instead of saying like the above one, you could have asked like you replied at last in this thread.

"I was getting error while reading PDF and specifically when i am going to particular page only
not on any other pages and also not any other place"


So problem with PDF file. It has some contents which are not supported by the currently installed pdf reader.

Hello everyone
Thanks for your replies
I was getting error while reading PDF and specifically when i am going to particular page only
not on any other pages and also not any other place

I think you are correct Zoran that disabling JIT won't stop the application from failing. I think that disabling JIT will only stop the popup from appearing. I understand that if the crash happens in something like Acrobat that we can't do anything about then the popup is not needed.

But then, do applications continue breaking down? I mean, are there errors in Event Viewer even after that? Because it doesn't seem logical to me that disabling JIT debugger would cause an .EXE to stop failing apart... Those two doesn't seem to be connected. I would expect that applications would continue breaking down, only not presenting the popup any more, but breaking down none the less which is equally bad.

Anyway, I personally use JIT debugger from time to time as a developer, and I could not afford disabling it on a developer machine. I suppose that is quite reasonable for many other developers too. It did happen couple of times in the past that some spooky error popped up on my computer and off course I did use JIT debugger to get into the matters because I am very concerned to know if something is not right on my computer. Those are typically driver-related problems that occur after Windows updates and JIT debugger may help you identify the faulty component and then to search for a solution or just to rollback it's update and then skip the available Windows update for that component. I had one very nasty problem with disk driver on laptop and that is how I solved it with help of JIT debugger. That is why I would never suggest a developer to disable it.

Zoran

Hi... 
I read some forums site regards this type of Error, error occurred while playing Nero, games and other applications too and solution provide in it is "Disable Visual Studio Just in Time debugger". When i was faced this type of error before some days.. i do disable JIT, after that i worked in VS, its going on well.
------------------------------------------- 

 I don't think this error is because of Acrobat..
 
 Because, long back i was facing same issue and no AcroRd32.exe installed on my system. 

 Later, i reinstalled VS and error gone.

 You can also disable it, refer.

 

I think Zoran is correct or at least close enough. It is difficult for me to see the image in the original question and then the qustion should provide more information instead of assuming we can understand just by looking at the image. Perhaps it would have helped to show just the error window without the entire desktop.

As best as I can see, it is just asking you if you want to debug the application and if you do then how. I can't tell what the application is but Acrobat Reader does seem buggy; I have been getting frequent updates for it and I assume everyone else does. If anyone has not gotten an update for Acrobat Reader recently then perhaps they should do an update.

Vilas,

Problem in this case is not with JIT debugger, but rather with Acrobat Reader. There is no point in reinstalling VS, because it's obviously registered as JIT debugger correctly. There is also no point in disabling debugging on a developer machine which has VS installed. The problem with Acrobat Reader should be addressed instead. If it turns out that failed application varies, i.e. it is not AR every time, then there is a different problem with machine or OS or something else and that's what should be reinstalled or otherwise fixed.

Zoran

Hi Mayur!
Suthish & Mahesh sir said that you reinstall VS.. before reinstall, may u do one thing? if its solve then no need of reinstallation. Because some days before i faced this type of error with OS not running VS. 

Error : JIT Debugger. so, its JUST-IN-TIME (JIT) DEBUGGINGPROBLEM. I think.  

Solution : To disable Just-In-Time debugging in Registry Editor. 

How to: 

Use the registry editor to delete the following registry keys:

·         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger

·         HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger

On a 64-bit operating system also delete the following registry keys:

·         HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger

·         HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\DbgManagedDebugger

----------------------------------------------------------------------------------------------------

If this reply hepls your post…then "MARK AS ANSWER"!

Mayur,

This message box reports an unhandled exception in Acrobat Reader, giving image name and process ID, and it offers you a chance to debug the faulty application. Since you have Visual Studio installed as a registered debugger, it offers you to use the VS as just-in-time debugger by starting new instance of VS and binding it to the faulty process. You may freely click Yes on this message box as it won't affect any already running instance of VS.

It will bring you to the place of failure in Acrobat Reader code and try to show you as much information as it can, though it might be quite small set of information available. When attaching to failed debug build process, that would provide you the full source code, call stack, etc. But in production cases like Acrobat Read you are probably not going to get anything more than the exception itself and probably very limited amount of readable information - everything else would be cryptic and in assembler. This is somewhat more than available in Event Viewer for this same failure.

To resolve the issue permanently, I suppose that you might just uninstall and then install again the Acrobat Reader, provided that AcroRd32.exe is always the one who fails.

Zoran

Hi,

Yes...

This is way of VS to tell you that "Don't overload me...". So let it be some seconds free if it is processing something..

don't click here and there when it is doing something....

For this situation just press No [ on figure shown above ].