Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Lim-Dul

  • Rank
  1. Is it perhaps the bug explained in this post?
  2. I don't know if that surprises anybody anymore but indeed the Vista bug seems to be gone or at least successfully circumvented in 12495. Thank you alus et al. ^^ And of course jsillup for his thorough testing procedure.
  3. Thanks - I had a lot of fun crashing uTorrent. ;-) I'm glad that Alus found a solution to this problem - one question, Alus - is it a workaround or a true fix? Do you know PRECISELY what causes/caused the crashes?
  4. Send me an PM or mail through the forums, jsillup - I followed your last testing procedure of rebooting the router but I'd be glad if there was an even easier method to reproduce the bug. ^^
  5. My findings: I downloaded utorrent-1.8-beta-7132 (earliest version on the list), utorrent-1.8-beta-7235 (last version on the list) and of course 7210 and 7211 to confirm jsillup's findings. The results are a bit "strange". None of the versions you provided, or rather I tested, crashed BUT none of them managed to open the proper port on my router using UPnP either... Update: Ignore all of the above. I see now that I will have to reboot my router between UPnP "deletions" as well (it's a security measure so that the same ports aren't re-opened after removing them manually). I'm re-testing the builds. P.S. It's still worth noting that the builds DIDN'T crash when they were unable to open the ports. MAJOR UPDATE! Now I followed jsillup's test procedure to the point (deleting UPnP ports and rebooting the router - note that it's a COMPLETELY different device with COMPLETELY different software). utorrent-1.8-beta-7132 - no crash utorrent-1.8-beta-7210 - no crash --------- utorrent-1.8-beta-7211 - crash utorrent-1.8-beta-7235 - crash YAY! Results! We managed to reproduce the bug quite precisely! On different routers and even different Vista versions since I'm running a 32-bit system! :-D Different setup, same results, it couldn't get more awesome than that - do you guys think you can pinpoint the bug now? For good measure I'm attaching the memory dumps of the last two crashes (despite their names the first one is from the exe numbered 7211 and the second one is from the exe numbered 7235 - as the devs you'll know better anyway ^^). 7184-utorrent_110a.dmp (105 KB) 7230-utorrent_b708.dmp (120 KB) Just to make you (and myself) happy I'm also pasting in the (Polish) error logs from the syslog. Nazwa dziennika:Application Źródło: Application Error Data: 2008-09-25 02:30:19 Identyfikator zdarzenia:1000 Kategoria zadania:(100) Poziom: Błąd Słowa kluczowe:Klasyczny Użytkownik: Nie dotyczy Komputer: ART Opis: Aplikacja powodująca błąd utorrent-1.8-beta-7211.upx.exe, wersja, sygnatura czasowa 0x48d9e98c, moduł powodujący błąd hnetcfg.dll_unloaded, wersja, sygnatura czasowa 0x4791a6c2, kod wyjątku 0xc0000005, przesunięcie błędu 0x7104c7fa, identyfikator procesu 0xedc, godzina rozpoczęcia aplikacji 0x01c91ea5de4b89b6. Kod XML zdarzenia: <Event xmlns=""> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2008-09-25T00:30:19.000Z" /> <EventRecordID>16615</EventRecordID> <Channel>Application</Channel> <Computer>ART</Computer> <Security /> </System> <EventData> <Data>utorrent-1.8-beta-7211.upx.exe</Data> <Data></Data> <Data>48d9e98c</Data> <Data>hnetcfg.dll_unloaded</Data> <Data></Data> <Data>4791a6c2</Data> <Data>c0000005</Data> <Data>7104c7fa</Data> <Data>edc</Data> <Data>01c91ea5de4b89b6</Data> </EventData> </Event> Nazwa dziennika:Application Źródło: Application Error Data: 2008-09-25 02:38:42 Identyfikator zdarzenia:1000 Kategoria zadania:(100) Poziom: Błąd Słowa kluczowe:Klasyczny Użytkownik: Nie dotyczy Komputer: ART Opis: Aplikacja powodująca błąd utorrent-1.8-beta-7235.upx.exe, wersja, sygnatura czasowa 0x48d9ed41, moduł powodujący błąd hnetcfg.dll_unloaded, wersja, sygnatura czasowa 0x4791a6c2, kod wyjątku 0xc0000005, przesunięcie błędu 0x7060c7fa, identyfikator procesu 0x9ec, godzina rozpoczęcia aplikacji 0x01c91ea70d1b86e6. Kod XML zdarzenia: <Event xmlns=""> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2008-09-25T00:38:42.000Z" /> <EventRecordID>16616</EventRecordID> <Channel>Application</Channel> <Computer>ART</Computer> <Security /> </System> <EventData> <Data>utorrent-1.8-beta-7235.upx.exe</Data> <Data></Data> <Data>48d9ed41</Data> <Data>hnetcfg.dll_unloaded</Data> <Data></Data> <Data>4791a6c2</Data> <Data>c0000005</Data> <Data>7060c7fa</Data> <Data>9ec</Data> <Data>01c91ea70d1b86e6</Data> </EventData> </Event>
  6. By the way - jsillup managed to pinpoint the first "problematic" release more precisely than I - I can just confirm that quite a few early alphas of 1.8 were working fine (with UPnP) and some later betas were not. I am also 99% sure that this MUST have something to do with UPnP now since I've been running the latest public beta (downloaded from the site) for 2 days without it crashing after I disabled UPnP - it crashed A LOT before.
  7. I don't think these are even NEW builds. So far the builds I (we) have tested were quite old because we wanted to track down where it all went pear-shaped.
  8. I have a completely different router (and with custom firmware to boot!) and experience the same crashes so it might not be router related. And yes, UPnP SEEMED to work correctly (that is, the ports were opened) as well. Now I know how to reproduce the bug - I don't have to REBOOT the router - I just need to close the ports uTorrent opened with UPnP. uTorrent apparently crashes each time it tries to set UPnP (or do sth. with it, dunno) - both on the router and, uhm, through Vista - the first time and ever after. Once the ports are set the program can apparently function normally until the next time it "tries to do something". It might very well be a bug in the Vista UPnP API - perhaps uTorrent uses some functions correctly but the OS handles them in a non-documented or simply buggy way.
  9. On a related note - with UPnP turned off uTorren (the latest beta) hasn't crashed ONCE and it has been turned on the whole day, it's been inactive and both downloading and seeding torrents. Virtually all scenarios were tested and I think jsillup has directly found a workaround. Now it begs the question if that's a Vista bug, a UPnP bug, a router bug, a uTorrent bug?
  10. Yo - thanks, jsillup! Alus already sent me some links to older versions I could test but I couldn't reproduce the bug reliably. This sounds as if it might have something to do with UPnP which is very probable since I started using UPnP in uTorrent a while ago after I got bored of opening ports on my router as I added computers to my home network. I'll disable UPnP and go back to old-school port forwarding and report back if this fixed the issue. If that is the case you'll not only be much closer to pinpointing the problem but also have a temporary workaround. P.S. I also checked that I have NAT-PMP port mapping enabled which, AFAIK, is only useful for certain routers, especially ones manufactured by Apple.
  11. Hmmmm... The latest version of uTorrent hasn't crashed for the last 6 hours. I'm getting suspicious, especially since it's inactive, so in the state that made it crash non-stop before. Update: OK, I decided to relaunch uTorrent since it obviously didn't want to crash. I'm "happily" reporting that this indeed made uTorrent crash almost immediately after relaunch. ;-)
  12. By the way - I just noticed one thing. When uTorrent "crashes" I, of course, get your custom "what do you want to do today" © window. However, the program doesn't actually feel like crashing - I never get any SYSTEM message that the application crashed AND I can keep the crashed window opened indefinitely while uTorrent functions perfectly fine in the background downloading and seeding and whatever else you use it for. ;-) Seriously, this seems less and less like a Vista bug and more like overzealous anti-crash protection or something. :-D P.S. Oh, gLes mentioned the same thing above. However, I don't even get the system crash warning afterwards...
  13. And It's pretty random. Usually it doesn't crash when downloading (now I noticed that contrary to my previous statement it DOES crash when downloading from time to time) but it does when seeding or being inactive. Some additional info for the previous posts - I have NOD32 but it's version 3 (and I added uTorrent to its exceptions like I wrote before).
  14. Yeah, I was told a few pages before. =) No, 1.7 didn't crash a single time for me so I prefer calling this the "1.8 bug". =)
  15. Any new uncompressed builds I can use to submit crash dumps? Because it keeps crashing just like I wrote several pages ago. =) Latest dump (compressed build): 12285-utorrent_0181.dmp (121 KB)