Shell crash error in application

V

vivek mishra

New member
Joined
May 26, 2017
Posts
2
[FONT=&quot]Hello,


We are looking for suggestions to possibly fix an issue our users are reporting.

They randomly get error :- "Application Name".Client.Shell has stopped responding.

Event viewer shows the following :-

Faulting application name: application.exe, version: X.X.X.X, time stamp: 0x5515edb6
Faulting module name: ntdll.dll, version: 6.3.9600.18194, time stamp: 0x569515fc
Exception code: 0xc0000374
Fault offset: 0x000e6054
Faulting process id: 0x159dc
Faulting application start time: 0x01d1a4a4b6ebc311
Faulting application path: D:\Program Files (x86)\Folder name\Application Name\application.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 854f9a97-1099-11e6-80dc-44a842249993



We see this coming up on Windows 2012 servers more often than Windows 2008.

We have tried to disable UAC/DEP/install desktop experience but it still occurs. We have also tried re-installing the app from fresh.

Happens in different modules but all the different modules call the same DLL when the crash happens

We also have a case open with Microsoft and they initially responded with their analysis :- They informed us that a component named Data Dynamics ActiveBar 2.0 Control which is used by the application is causing this problem. In this specific scenario, it is used in the DLL where we see the crash happen. ActiveBar component is trying to free up some memory in improper way and is causing this crash. It seems the conclusion was :- that Active bar 2 control is trying to free a memory and that encounters heap corruption. VB6 runtime internally manages memory and frees it automatically when unused. So, it’s the internal VB6 operation which is causing issue

We have tried to comment out the method "we think" is causing the crash, in as many places as we could but it still crashes.The logs show the crash happening at a different place now. [/FONT]
[FONT=&quot]Looking for suggestions to help fix this. We can provide more details if needed. [/FONT]
[FONT=&quot]Searched in the forums and saw this. Is this something worth trying and could this be related? Random crash in NTDLL.dll with PlaneProjection animation

While searching I came across this forum and a thread :-
https://www.sysnative.com/forums/wi...7-stackhash-appcrash-issue-windows-7-sp1.html

It seems @niemiro was able to help fix this. I followed the instructions and downloaded a dump. It seems the last module before the crash is Actbar2.ocx , module version 2.0.1.1109, Module path :- C:\\Windows\SysWow64\Actbar2.ocx. This seems consistent with what microsoft stated but not sure if this is the cause of the crash. (Note error is random and comes up when following the same process repeatedly about 15-20 times - this is also inconsistent).

Can someone please help with providing some directions/assistance with this?

Thank you! [/FONT]
 
You say the error is inconsistent and happens after some 15-20 times? My first inclination would be some form of race condition that causes garbage collection to fail because the memory is still in use somewhere else. That would be consistent with the inconsistencies you are seeing with the errors. In that case, check for module/memory access and make sure it is thread safe.

A memory leak through Active bar 2 is another possibility. Reference: Active Bar 2 (Actbar2.ocx) leaks memory - Our ComponentOne - Our ComponentOne

The other possibility is a set of variables that are created but never assigned to, resulting in random behavior when the memory is freed because sometimes the values are well defined and other times they are not. That scenario may be more difficult to track down, especially if it is occurring within the Active bar 2 extension.

You could also try different display drivers per the first link you provided. Are you suspecting some conflict with the UI and display adapter drivers?


I am curious about the generic naming you used for the application.exe file path. Is the software that is ceasing to respond proprietary?
 
Last edited:
writhziden said:
You say the error is inconsistent and happens after some 15-20 times? My first inclination would be some form of race condition that causes garbage collection to fail because the memory is still in use somewhere else. That would be consistent with the inconsistencies you are seeing with the errors. In that case, check for module/memory access and make sure it is thread safe.
Click to expand...

A memory leak through Active bar 2 is another possibility. Reference: Active Bar 2 (Actbar2.ocx) leaks memory - Our ComponentOne - Our ComponentOne

The other possibility is a set of variables that are created but never assigned to, resulting in random behavior when the memory is freed because sometimes the values are well defined and other times they are not. That scenario may be more difficult to track down, especially if it is occurring within the Active bar 2 extension.

You could also try different display drivers per the first link you provided. Are you suspecting some conflict with the UI and display adapter drivers?




Yes it is proprietary. (I tried to quote but may have got it wrong. I am not used to forums a lot)

the strange thing is its not re-creatable on every server. In some instances we got the application installed locally (win 7) and the users stop getting the errors.
We commented out Tbr.RecalcLayout since that seemed to be where it was crashing but it started crashing at other places. some users are more affected than others even though they connect to the same server(some dont get it at all). We have rebuilt user profiles, re-installed the app, toggled with permissions etc. but no use.

Its more of an issue on Windows 2012 R2 (only one instance discovered recently of the server being 2008 R2 but that is also not confirmed since we found that desktop experience is not enabled and that does cause some issues + on that server we are getting the crash every time). In a lot of instances we have been notified that the issues started after upgrading to 2012 R2 - which gives more credibility to our observation.

I will look at the link to see if that helps.

Thanks for your reply and assistance. If you can think of something else or any further assistance would be immensely appreciated !!
 
Last edited by a moderator:

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top