 |
David256 Beginner
Joined: 07 Nov 2006 Posts: 22
|
|
|
 |
Vijilante SubAdmin

Joined: 18 Nov 2001 Posts: 5187
|
Posted: Sun Nov 25, 2007 4:43 pm |
It uses http. There is a known bug in how it works when you have an http proxy defined. That is why I am always posting my crash dumps instead of sending them.
|
|
_________________ The only good questions are the ones we have never answered before.
Search the Forums |
|
|
 |
David256 Beginner
Joined: 07 Nov 2006 Posts: 22
|
Posted: Mon Nov 26, 2007 10:33 am |
Hrm, I don't connect through a proxy but it still doesn't work for me. No big deal, I don't mind posting or manually emailing the dumps instead.
|
|
|
 |
Guinn Wizard
Joined: 03 Mar 2001 Posts: 1127 Location: London
|
Posted: Mon Nov 26, 2007 2:44 pm |
Mine fails more often than not too and I don't use a proxy.
|
|
_________________ CMUD Pro, Windows Vista x64
Core2 Q6600, 4GB RAM, GeForce 8800GT
Because you need it for text... ;) |
|
|
 |
Tech GURU

Joined: 18 Oct 2000 Posts: 2733 Location: Atlanta, USA
|
Posted: Mon Nov 26, 2007 3:42 pm |
It's a little finicky, but it's firewall dependent. I configured my firewall to always allow CMUD and CMUDPro and now I don't really have an issue with it. More often than not if it fails the first time it definitely works the second time.
I think there may be a timeout window to actually to create and send the report because when I get failures it seems to happen happen more when I choose to include the screen shot |
|
_________________ Asati di tempari! |
|
|
 |
Zugg MASTER

Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Mon Nov 26, 2007 5:42 pm |
Sending crash dumps is always going to be tricky. Keep in mind that a crash dump is usually generated by something causing corrupt memory (like a memory pointer problem...also called an "access violation"). Trying to pop up a window and then properly send the data via a network connection when the application is already screwed up can be hard.
But as Tech mentioned, I've seem more problems when using proxy servers or firewalls. Also, the crash dump system uses whatever proxy settings are set for Internet Explorer in your Internet Options control panel, regardless of what browser you actually use. So if you are using Firefox, you should still check these settings to see if they are set correctly.
In general, try to get your crash dump sending to work. When you use the automated send option, then they get automatically added to our bug tracking database. When you send them via email or post them to the forums then I have to manually add them, so they might get lost or forgotten. And it's definitely more work for me to track those.
Also, the automated crash dump reporting will combine multiple reports of the same crash into a single topic in my database. When I process the dumps posted in the forum and in email manually, there isn't any easy way to combine them with other reports of the same bug.
From a technical point of view, I am using the MadExcept components for handling the crash dump generation. And it just opens a direct HTTP socket to the www.zuggsoft.com server. It is *not* using any sort of mail. It should be a direct HTTP connection, so if Internet Explorer can access www.zuggsoft.com, then the crash dump system should be able to do it too. |
|
|
 |
|
|