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

Code completion problems (segfaults)

<< < (3/4) > >>

280Z28:
Continuing the steps above (I hit the 20000 char limit):

- Opened, let it sit until CPU usage dropped. Exited, Crashed.
- Opened, let it sit until CPU usage dropped. Exited, Crashed.
- Opened, let it sit. Crashed without notice after 2-3 seconds.
- Observed that my memory usage with Code::Blocks open was around 530-540mb, I have 512 megs.
- Exited Trillian and some explorer (not internet explorer) windows and reopened C::B. Let it sit until CPU usage settled, mem usage at 490mb. Exited, no crash.
- Opened Trillian, then opened CB. Let it sit, memory rose to ~530 and CB crashed without warning except a new window popped up saying "the memory could not be read at 0x13000000"
- Copied this whole message into notepad and closed Firefox which freed up 70 megs or so. Trillian still open. Opened CB, waited for it to settle, (~390mb) went to exit, crashed...??
- Opened CB, crashed after ~3 seconds no warning.
- Waited for a while (couple minutes), opened it, ~390mb stablized, exited, no crash
- Opened Photoshop and Acrobat, then open the CB project. Memory stablized at 505mb. Went to exit, and it hit a quick spike at 533 and crashed.
- Closed Acrobat and waited for a while (maybe Windows was reloading from paging after the low memory condition?). Opened CB, stable at 470, exited, fine.
- Opened firefox to google homepage. Opened CB, stable at ~490, exited, fine.
- Opened a few firefox tabs, Opened CB, slowly rose to 507 then spiked to 540 and crashed.
- Closed Photoshop, let it sit for 30seconds or so. Opened CB, went to ~410 then spiked to 440 and crashed.
- Closed Firefox, let it sit for 30seconds or so. Opened CB, stablized to ~390 and didn't crash. Went to exit, hit a ~440 spike and crashed.
- I've attached the logs from all this.

[attachment deleted by admin]

280Z28:
Updated to 1755
Turned off global includes processing
Opened a bunch of programs - mem usage before opening CB 611mb
CB opened fine, closed fine when I did after a while
Opened, turned on global processing and closed to save settings
Opened, Crashed less than 0.5 seconds after the GUI appeared.

grunerite:

--- Quote from: 280Z28 on January 14, 2006, 10:35:09 pm ---Updated to 1755...
Opened a bunch...
Opened, turned on global processing...
Opened, Crashed less than 0.5 seconds..

--- End quote ---
Let off the accelerator. Slow down! You're gonna burn it up. Get some snow chains.  :)

rickg22:
Darn it... i can't replicate it!

I'm using rev. 1756. I'll follow local and globals now, but without parsing the preprocessor directives.

MortenMacFly:

--- Quote from: rickg22 on January 15, 2006, 05:55:30 am ---Darn it... i can't replicate it!

--- End quote ---
I can't, too. It works well for me. For me this sounds like a memory lock-up. I wonder whether this really is a C::B problem or (maybe) bad memory... or another application corrupting the memory?! 280Z28: What about the other applications that are running? Do you experience other application crashes as well? Do you experience the same crashes if you're using one of the nightly builds (including the "nightly" wxWidgets libs)? Morten.

Navigation

[0] Message Index

[#] Next page

[*] Previous page