NS Instability on high-end computer
DHawthorne
Posts: 4,584
I almost never have a problem with my work computer, but last night I needed to add a tweak to my home system, and didn't feel like firing up the laptop just for that. So I ran NS on my home computer for the tweaks.
I didn't add more than than a dozen or so lines ... but NS must have crashed a half dozen times. It crashed when I used the "Goto SEC" several times, it crashed when I used "Goto SUB." It crashed once just scrolling through the source. And, to top it off nicely, it crashed when I was done and closed the program. I was stunned ... and thought maybe I had an older version running at home, so I ran Web Update, and it was already current. Version 3.1.0.374. These crashes had nothing to do with IP connection either. Now the main differences between my work machine and my home machine are largely performance ... and by that I mean, my home machine is much faster, has much better graphics, and overall is a much better computer. Just incidentally, the home PC has in Intel processor, and my work machine an AMD, but I doubt that is relevant. Furthermore, when I shut down for the night, the computer hung shutting down ... which never happens on that PC, but actually happens all the time on my work PC, leading me to believe even that may be related to the NS instability.
So what's the deal? Are there issues with NS that I just never noticed because they didn't affect my work computer that much? Is anyone else having frequent crashes like that, or has anyone found a way to make it more stable?
I didn't add more than than a dozen or so lines ... but NS must have crashed a half dozen times. It crashed when I used the "Goto SEC" several times, it crashed when I used "Goto SUB." It crashed once just scrolling through the source. And, to top it off nicely, it crashed when I was done and closed the program. I was stunned ... and thought maybe I had an older version running at home, so I ran Web Update, and it was already current. Version 3.1.0.374. These crashes had nothing to do with IP connection either. Now the main differences between my work machine and my home machine are largely performance ... and by that I mean, my home machine is much faster, has much better graphics, and overall is a much better computer. Just incidentally, the home PC has in Intel processor, and my work machine an AMD, but I doubt that is relevant. Furthermore, when I shut down for the night, the computer hung shutting down ... which never happens on that PC, but actually happens all the time on my work PC, leading me to believe even that may be related to the NS instability.
So what's the deal? Are there issues with NS that I just never noticed because they didn't affect my work computer that much? Is anyone else having frequent crashes like that, or has anyone found a way to make it more stable?
0
Comments
I recently had the same experience with my laptop, running XP Pro as the OS. Upgraded a few weeks ago to NS3 and after multiple crashes, I reverted to NS2 2.8.285. Frankly I can't remember the last time NS2 crashed on my laptop.
Paul
I run it on the following machines.
1 Dell Dimmension 4200 - Windows 7Pro (no problems.)
1 Dell Inspiron Laptop Window7Pro (no problems)
I also run it on a Mac Miini Intel Duo 1.8Ghz - OSX 10.5 with a VMWare PC (single processor - 1 Gig RAM) on XP Pro and it hasn't given me any greif.
IREdit and TPDesign are still very crash-happy for me on any of my machines desktop or lappy.
I am usinag a 64 bit Windows 7 machine and found that I HAD TO install on my "C" drive. I normally leave C for OS only and put everything else on other drives. When doing the install, the first screen after accepting the licnese agreemnt is to pick the destination folder. When I clicked "Browse" it hung up on me. This was ONLY with NS, worked fine on API, TP4 and the rest all installed onto my other drive with no issues.
Same problem here. It's not that it has to be c:, it has to be the default directory as the installer completely craps itself if your try to bring up the 'browse...' dialogue (tried multiple times, on multiple machines).
In regards to NS stability once it's installed haven't seen any of those issues here. Hums along nicely on a Dell Latitude E6500 (XP SP3, Core2 duo @ 2.53GHz, 2GB ram), MacBook Pro (Win7 under VMWare - allocated 2 cores, 2GB ram), Custom built Core2 Quad @ 2.4GHz, 8GB ram, Win7 x64. TPD4 on the other hand...
Worst I got in NS was things like "No error Occurred".
And I can confirm what Phreak said. It DOES NOT like the browse button being used in the installer. This crashes the freaking installer. (Depending on what you are installing)
Best computer error EVER!
I still have NS3 crash on bootup when it tries to resume an old workspace . . . constantly. Multiple times a week I'll have to start NS3 4 or 5 times before it actually stays started up . . . but it seems to do that even on my crappy work computer too, so I don't think it's anything about the computer being high end. I think it's just that NS3 was coded by drunken monkeys.
I used to have problems all the time but it hasn't seemed so bad lately or maybe I've just grown oblivious to it. I think my problems were when opening large .apw files which had several files open in the workspace and I think this was fixed (improved upon) in one of the NS revisions. I rarely use the GO TO stuff since I tend to fold alot with multiple define "whatever" sections which makes scrolling a little easier for me.
I also doubt it was drunken munkeys, seriously don't you always seem to come up with waaaaay better stuff when you're drunk?
Sometimes it just simply doesn't want to open. Can see it on the Process tab, but no window will pop up.
I'm using a Intel Centrino T2300 @ Windows XP SP3.
Goto... has been working fine, but I barely use it to be honest.
NS3 has been quite stable on this Laptop, can't say the same about Mr. TPDesign4 tho, which must be the buggiest software I might ever used. (Got to love when, during the save process, some buttons magically aquire background images, and buttons get out of place, and you don't notice, till it's on the TP already)
Sent from my HERO200 using Tapatalk