Massive lag spike / Computer Freeze

Comments

• Thyth

  January 2009

  What are your system specifications (specifically CPU model and frequency)?
  
  What kind of key were you trying to generate? 512-bit? 768-bit? 1024-bit?
  
  RSA key generation takes a while.
• SnowFire789

  January 2009

  This was DIRECTLY after the 10 seconds.
  Not before I hit the keygen.
  
  Kay, it goes like 3...2....1.. And changes to step two? Yea, it freezes THERE.
  Redownloading atm.
• ddeimos

  January 2009

  Same here... Testing Tribes 2 on an MSI Wind.
  
  After mouse movement/10 second timer... the interface lags.
• ccliff

  January 2009

  Thyth January 2009

  What are your system specifications (specifically CPU model and frequency)?
  
  What kind of key were you trying to generate? 512-bit? 768-bit? 1024-bit?
  
  RSA key generation takes a while.

  
  I'm also getting this issue. Here's what happens:
  1. get to the key generation screen, where it asks you to move the mouse for 10 seconds,
  2. wiggle the mouse inside the box, which generates a few white dots sometimes
  3. when the countdown finishes, the whole thing drops to less than one frame a second,
  4. manage to get the mouse cursor to the "generate key" button, and click on it, which completely freezes mouse input.
  
  I've tried letting it run for 5-10 minutes and nothing really happens, so I check the task manager and tribes2.exe is pegged at 50% cpu, and rubyintersect.dll is pegged at 50% cpu. At this point I kill them and find this forum. I'm running an 8-year-old computer with a 1 GHz Athlon processor, and an ATI Rage 128 (32mb) AGP graphics card. It's running the key generation in the default RSA-512 mode.
• Krash

  January 2009

  At the point you're describing, a loop runs a bit of code at short intervals. It only runs until the key is generated, so if you're able to click the button it may eventually go through.
  If not, we may be able to find a workaround later.
• ddeimos

  January 2009

  Another thing...
  
  After 5 mins... alt-tabbed out - killed the ruby~.dll process, returned back to the interface. And saw the 'key generated' message. :-\
  
  Then some other issue crops up on submiting the rest of step 3, which is ain't the subject of this thread.
• Krash

  January 2009

  If you killed the ruby interpreter's process while generating a key, that key will be broken. Just a heads up.
• ccliff

  January 2009

  It finally worked for me. I had it in windowed mode just so I could tab out and stuff, it might not be necessary but it probably won't hurt. Waggle the mouse for 10 seconds, then click the button. Alt-tab for like 15 minutes and check on it periodically. It took 11 minutes for me, so just keep waiting. Eventually it'll finish and you can press "next step".
• Thyth

  January 2009

  The system was developed on a system with a 2 Ghz Intel Core 2 Duo processor, and the estimated key times are based on systems with similar specifications. On this system I manage a 512-bit key generation in under 90 seconds.
  
  That 1 Ghz Athlon is pretty old school though. 11 minutes is pretty impressive.