Troubleshooting Unitrunker crash

Status
Not open for further replies.

bpsmicro

Member
Joined
Dec 19, 2002
Messages
236
Reaction score
5
Location
near Ottawa; Canada
With the latest Unitrunker build, crashes are few, but I've noticed a trend that may assist in troubleshooting:

Normally I leave it sitting on my desktop, monitoring a system. When it does crash all by itself in these cases (I'm not even touching it), it's *always* as soon as I click on a dropdown on a web page in my browser (Firefox 3.0.1).
In other words, I'm surfing away, on a page with a dropdown in a form, and I click the dropdown, and Unitrunker barfs.
Of course, if I relaunch Unitrunker and go to the same page, it won't happen again. Many more hours or days will pass without me seeing it again.

I have Visual Studio 2008 on my primary machine. If you want to put together a debug build I can launch into the debugger next time it crashes and try to narrow down where it's crashing. PM me if you want to try that.

Brad.
 

SCPD

QRT
Joined
Feb 24, 2001
Messages
0
Reaction score
110
Location
Virginia
Thanks Brad. The next release - which includes fixes for some harder to reproduce crashes - may address the problem you describe.
 

bladeslap

Member
Joined
Nov 7, 2008
Messages
2
Reaction score
0
Location
Piscataway, NJ
Good afternoon - First, thanks for all the hard work you put into Unitrunker -- I had developed a similar application in the DOS days using a slicer and a 2006 scanner and optoelectronics board - Problem is I never quite got into windows API and am not sure if the ISRs would work fine - With that aside, I have been using your program for the last few days ... I've tried it both under Vista and server 2003 - Because of the location of the VISTA computer (Much higher in the house), I have to run it on there -I get crashes about once a day - Here's the data:

Faulting application Uniform.exe, version 1.0.0.5, time stamp 0x48fd7958, faulting module Uniform.exe, version 1.0.0.5, time stamp 0x48fd7958, exception code 0x80000003, fault offset 0x000a2025, process id 0x43f8, application start time 0x01c944d99b1e2a5e.

I'm using the Soundcard input ... I might try the slicer just to see if it makes a difference (perhaps the faulting module deals with the audio i/o portion? Anyway, curious as to whether the data I attached will be of any use and if you have plans to release a future version.

Thanks -
 
Status
Not open for further replies.
Top