Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

C::B fails to start on Windows (Rev 4407)

<< < (4/5) > >>

MortenMacFly:

--- Quote from: TDragon on August 27, 2007, 05:27:21 pm ---In multithreaded apps, random or "stochastic" symptoms indicate multithreading problems 90% of the time.

--- End quote ---
Maybe, but this would not explain why it crashes at home 100% and here at work 0%.

TDragon:

--- Quote from: MortenMacFly on August 27, 2007, 05:34:59 pm ---Maybe, but this would not explain why it crashes at home 100% and here at work 0%.

--- End quote ---
Certainly it could -- your home PC might be moving fast enough to (for example) slip into a race condition before a semaphore in another thread gets signaled; or it might be slow enough that (for example) a thread that's waiting for data mistakenly decides to act on it before it's received it. The work PC, on the other hand, follows the expected path because it's not too fast or not too slow.

rickg22:
I hate to say this, Thomas - but didn't we all agree on "If it ain't broke..."?

I had reverted your code that time not only because I didn't understand it, but because it actually crashed. What I didn't understand was WHY it crashed. After I had reverted it, CB stopped crashing at certain addresses but still crashed on others. Then I fixed my code and everything was fine.

But do whatever you want, it's your code - as long as my 4291 rev plays fine, NP for me.

thomas:

--- Quote from: rickg22 on June 26, 2007, 04:24:13 am ---I've tried to analyze the Abstractjob code, but it's too complicated for me to understand the program flow. I don't even know if the ORIGINAL code is correct!  :?
--- End quote ---
You know, Rick... the original code worked fine for 10 months before that... :)

But anyway, I'm through with it. I'll do the revert myself. Just don't ask me again if your code leaks and crashes.

rickg22:
Thanks! :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page