Page 1 of 1

SOLVED? Crash

Posted: 07 Apr 2015 12:05
by vha
Using 10.23b2

- Open a large file (export to .reg file of HKEY_LOCAL_MACHINE, 390MB on my system)
- In Windows Explorer, right click on another (small file), chose RJ TextED
--> Following crash window is displayed:

Code: Select all

---------------------------
EurekaLog 7.2.1.0 crash report
---------------------------
ERangeError: Range check error



ESysInfo.GetVirtualMachineType (Routine: 000000000046EDF7:000000000006DDF7)



(report generated by ESysInfo.BasicInitDoneErrorHandler)

Press Ctrl + C to copy report to clipboard
---------------------------
OK   
---------------------------
vha

Re: Crash

Posted: 07 Apr 2015 12:15
by Rickard Johansson
I think it's the good old exception catcher software issue with virtual software, like when VMWare Workstation is running... There's nothing I can do about it. The exception catcher software is not included in the final release. It's only included in debug and beta versions.

Re: SOLVED? Crash

Posted: 07 Apr 2015 12:24
by vha
Did the following:

- stopped all VMWare services
- stopped vmware-tray.exe process
- launched TextED, opened the big .reg file
- right clicked on a small file, RJ TextED

--> still have the crash

it doesn't crash if I only open smaller files and VMWare WorkStation was not running (only the services were)


vha

Re: SOLVED? Crash

Posted: 07 Apr 2015 13:27
by Rickard Johansson
I get the same error when just opening the program while VMWare Player is running (at least sometimes). It seems to be very random. Sometimes it runs just fine, but after some work in VMWare Player, or opening and closing browsers etc. it suddenly wont run again.

Do you still get the same error if you restart the computer?

Re: SOLVED? Crash

Posted: 07 Apr 2015 13:33
by vha
Yes:

- Reboot
- No VMWare WorkStation or Player running
- Open HKLM.reg
- Open small file
--> Crash

vha

Re: SOLVED? Crash

Posted: 07 Apr 2015 14:15
by Rickard Johansson
Well, the crash occur in the exception catcher software and not in the main program. It's not 100% reliable (and never has been) but it's still usable in a beta build to catch problems...