Crash Reports - Question to N3V

[NSWGR_46Class]

Does anyone read the crash reports that trainz ask you to fill out when it crashes anymore

Are they worth filling out or is it flogging a dead horse expecting up date for TS12 now TANE is just around the corner

 

[gawpo50]

Does anyone read the crash reports that trainz ask you to fill out when it crashes anymore

Are they worth filling out or is it flogging a dead horse expecting up date for TS12 now TANE is just around the corner

Probably doesn't hurt to send the report

 

[NSWGR_46Class]

Well do not want to be filling in the things 10 times a day if nobody reads them - or there not going to lead to any change

Probably doesn't hurt to send the report

 

[shaneturner12]

I'm not sure if they still actively monitor the old crashreport address, although if it's crashing frequently it means something is seriously wrong with your version.

Shane

 

[RRSignal]

I would consider moving the Trainz crash reporter, xcrashreport.exe elsewhere so that it's effectively removed. It's in Trainz' bin folder. I've noticed a very strong correlation between software instability and crash reporters over the years. I have no idea why - perhaps it's poorly-implemented functions in the runtime libraries, perhaps something else.

 

[shaneturner12]

That may not be a good idea to do as it's part of the browser components of Trainz (which seems to have parts of Firefox). As I said though, if it's a frequent issue I would start looking into what is being done at the time of the crash (and quite often the crash reporter creates a ZIP file in the temp folder that can be sent to N3V via their helpdesk or TrainzDev address).

Shane

 

[NSWGR_46Class]

But if they're not developing TS12 anymore the reports are in theory useless and if nobody then reads them pointless.

That may not be a good idea to do as it's part of the browser components of Trainz (which seems to have parts of Firefox). As I said though, if it's a frequent issue I would start looking into what is being done at the time of the crash (and quite often the crash reporter creates a ZIP file in the temp folder that can be sent to N3V via their helpdesk or TrainzDev address).

Shane

 

[pcas1986]

I'm sure I read a post a few months back by Windwalkr that the dumps were not of much use to N3V. Which begs the question of why they are there. Based on my own software dev experience and comments on TANE bug reports, I suggest raising a problem report and providing sufficient information to allow N3V to reproduce the problem.

However, given that N3V are focussed on TANE, I'm not sure how much notice they might take unless it is a problem that could carry over into TANE.

FWIW I stopped sending them in. Especially when I suspect I caused the problem with a dubious (scripted) asset in the first place.

Cheers

 

[JCitron]

When I have received the crash reports I have sent them in the past, however, more recently I have performed forensics on them myself using Microsoft's Window Debug tool (windbg). The actual crash dump files are located in the \Users\{login name}\\AppData\Local\CrashDumps.

Using Windbg and the Event Viewer, I was able to determine what was going on with a compatibility issue I had with TS12 and Windows 8.

John