| Author |
Message |
muppetry
Joined: 13 Dec 2006 Posts: 14
|
Posted: Thu Dec 14, 2006 6:26 pm Post subject: |
|
|
| Yes - I tried it from another account and it behaved exactly the same. Are you running on Intel or G4/5? I'll try it on another Intel machine, a G4 and a G5 for completeness. |
|
| Back to top |
|
 |
stanbusk Site Admin
Joined: 28 Dec 2005 Posts: 2379
|
Posted: Thu Dec 14, 2006 6:28 pm Post subject: |
|
|
| I have tried on a MacPro 3Ghz, an iMac Intel 2 Ghz and a G5 2 Ghz. Same results here. It is important I can reproduce first. |
|
| Back to top |
|
 |
muppetry
Joined: 13 Dec 2006 Posts: 14
|
Posted: Thu Dec 14, 2006 6:43 pm Post subject: |
|
|
| OK - you are testing on basically the same machine - the Mac Pro. I'm running 10.4.8. I'll get back to you when I've figured out if this problem is specific to this machine. |
|
| Back to top |
|
 |
muppetry
Joined: 13 Dec 2006 Posts: 14
|
Posted: Fri Dec 15, 2006 3:07 am Post subject: |
|
|
I've now tested this on a G4 Powerbook and a G5 PowerMac as well as the Mac Pro, all running 10.4.8. Its behavior is the same on all three. Are you running 10.4.8?
I've tried using different nameservers, restoring factory settings, changing retry and timeout settings, and throwing away the preference file. Same result in all cases. I don't know why you are not seeing it, but this is a bug. |
|
| Back to top |
|
 |
stanbusk Site Admin
Joined: 28 Dec 2005 Posts: 2379
|
Posted: Fri Dec 15, 2006 4:40 pm Post subject: |
|
|
We use 10.4.8 and Windows XP SP2 here. I can't reproduce the problem. The code is correct, the timeout timer is destroyed right after the test is done. On your case it looks like that timer is never destroyed and continues to run. The code is clear, we stop, close and destroyed that timer. Do you have something installed on your computers that could change threads or timers behaviors? Also note that I have never received other reports with such problem so far. If it were a bug it wouldn't be in the application but elsewhere.
Anyway, I can add more security to the code to avoid the problem to appear. Please open a support ticket so I can give you a link to a new compile. |
|
| Back to top |
|
 |
muppetry
Joined: 13 Dec 2006 Posts: 14
|
Posted: Fri Dec 15, 2006 5:19 pm Post subject: |
|
|
I'm not aware of anything on my machines that could interfere with your code. The machines that I've tested it on so far have different architecture and different and independent software installations. It happens even when I boot in safe mode. Also, as I mentioned before, this problem doesn't occur with addresses tested via a list loaded from a file, even if it only contains one address. Without seeing your code I can't assess the significance of that, but maybe you can.
I would agree that from your perspective, this may appear to be a problem with my machines, but I can't figure out what could possibly cause that. I considered network/firewall issues, but that doesn't seem to explain why the program successfully checks the individual addresses (and says so, briefly) but doesn't stop, or why lists work just fine. Can you suggest any other tests I could try to attempt to pin this down?
No one else who has read this thread has commented either way on the subject - it would be nice to have some additional data. |
|
| Back to top |
|
 |
muppetry
Joined: 13 Dec 2006 Posts: 14
|
Posted: Fri Dec 15, 2006 10:37 pm Post subject: |
|
|
| FYI - I've now tested this on another G5 PowerMac running 10.4.8 on a different network (not mine) and it too behaves just the same, including in safe mode with no other applications running. I no longer believe that this is not a problem with eMail Verifier itself. Shall I open a support ticket? |
|
| Back to top |
|
 |
stanbusk Site Admin
Joined: 28 Dec 2005 Posts: 2379
|
Posted: Sun Dec 17, 2006 6:52 pm Post subject: |
|
|
| Yes, please open a support ticket so we can sort that out. |
|
| Back to top |
|
 |
|