Author Topic: thread problems (exactly the opposite how it should be)  (Read 620 times)

0 Members and 1 Guest are viewing this topic.

Offline danmer

  • Camper
  • ***
  • Posts: 466
  • crabhead
thread problems (exactly the opposite how it should be)
« on: November 01, 2008, 07:30:01 am »
I thought it was a truth commonly acknowledged that threadfunc bugs on linux while working perfectly well on windos. Well it wasnt the case with me when i tried this today. What this piese of code does is that it gets the page from a separate thread, so that it doesnt lag up people in the server (it gets current timestamp in this case).

What happens when i try to run this on linux (debian) is surprise surprise, it runs pretty dam well. Without the gettickcount check i was getting a lot or errors (access violations, stack overflow and whatnot), but when letting it wait for a while between the requests it worked well.
But again on windos (winxp sp2) it keeps on throwing "(getpage): Out of Global Vars range" errors at me, even with delay set to 300.

Any thoughts?