Chemtable Software Forum

Posted: **Wed Aug 30, 2017 3:23 pm**

Will this program crash the same way as Reg Organizer do on your system?

Yes, within moments. I've attached a screencap to show how far it gets.

crash.jpg

Posted: **Wed Aug 30, 2017 3:54 pm**

Sorry, forgot to add the log generated:


============================================
Start: 30/08/2017 16:19:24
FirstStartAsync Begin
GetProcessMemoryInfo:
    WorkingSetSize=12120064 (11 MB)
    PagefileUsage=4902912 (4 MB)
    PeakWorkingSetSize=12120064 (11 MB)
    PeakPagefileUsage=4902912 (4 MB)
GetProcessMemoryInfo:
    WorkingSetSize=12152832 (11 MB)
    PagefileUsage=4902912 (4 MB)
    PeakWorkingSetSize=12152832 (11 MB)
    PeakPagefileUsage=4902912 (4 MB)
~TProgressObservation Impl = 0
TRegSnapShotAsync Create 116c810
~TRegSnapShotAsync Impl = 116c810
FirstStartAsync End
FirstStartAsync End
TProgressObservation::TImpl 125c430
TProgressObservation, MaxKeysValues=2119696
TProgressObservation bool(ProgressFunc)=1
TRegSnapShot::TImpl RpcCall
AddDefaultExcludes Begin
TProgressObservation Execute Start 125c430
TProgressObservation Execute bool(ProgressFunc)=1
TProgressObservation Execute 1 125c430


============================================
Start: 30/08/2017 16:20:45
FirstStartAsync Begin
GetProcessMemoryInfo:
    WorkingSetSize=11988992 (11 MB)
    PagefileUsage=4911104 (4 MB)
    PeakWorkingSetSize=11988992 (11 MB)
    PeakPagefileUsage=4911104 (4 MB)
GetProcessMemoryInfo:
    WorkingSetSize=12021760 (11 MB)
    PagefileUsage=4911104 (4 MB)
    PeakWorkingSetSize=12021760 (11 MB)
    PeakPagefileUsage=4911104 (4 MB)
~TProgressObservation Impl = 0
TRegSnapShotAsync Create 150c810
~TRegSnapShotAsync Impl = 150c810
FirstStartAsync End
FirstStartAsync End
TProgressObservation::TImpl 15fc430
TProgressObservation, MaxKeysValues=2119696
TProgressObservation bool(ProgressFunc)=1
TRegSnapShot::TImpl RpcCall
AddDefaultExcludes Begin
TProgressObservation Execute Start 15fc430
TProgressObservation Execute bool(ProgressFunc)=1
TProgressObservation Execute 1 15fc430

Posted: **Thu Aug 31, 2017 8:06 am**

Thank you for sending the information.

We cannot find the problem in our code in this part of the application. Please try to disable the Data Execution Prevention to see how this will affect the problem. To do this:

1. Go to Start
2. Write CMD and run it as an administrator
3. Type : bcdedit.exe /set {current} nx AlwaysOff
4. If you want to know if DEP has been disabled type "bcdedit" and NX should be AlwaysOff

Restart your Computer to apply.

To enable, type:

bcdedit.exe /set {current} nx AlwaysOn

To learn more, see: https://www.youtube.com/watch?v=BexFZPCC5dY

Posted: **Thu Aug 31, 2017 12:51 pm**

Thanks for looking into this further...

I turned off DEP and it made no difference at all. That doesn't seem to be the problem.

Posted: **Thu Aug 31, 2017 3:03 pm**

We'll try to reproduce the problem. If you have any thoughts how to do this on an arbitrary system (for example, installing some specific software you have), please let me know.

Posted: **Thu Aug 31, 2017 6:43 pm**

I will give it considerable thought, thanks.

Chemtable Software Forum

Crashing on monitoring

Re: Crashing on monitoring

Re: Crashing on monitoring

Re: Crashing on monitoring

Re: Crashing on monitoring

Re: Crashing on monitoring

Re: Crashing on monitoring