Squee Runtime Issues

[friarsol]

Hey Squee,

Was the issue Chris posted in the other thread the issue you are having? What's your specs on your machine? OS, Memory, CPU, the works? I'm considering creating an Ubuntu VM that has the Forge source installed and hooked up to the SVN, this way I can verify everything works. But if you're machine can't handle running a Virtual Machine than it isn't worth it. I know it's not the best solution (I don't know anything about why the Progress Bar would cause issues) but booting a VM to Forge it up, could at least give you something that's functional, if you're computer is able to, and you're willing to give it a shot.

Do the releases work for you either?

[moomarc]

Sol, I asked Squee some time ago on the Card Development/Contribution threads if those were the errors and he confirmed that they were. You'll have to wait for the specs from him though.

Thought this might be helpful though (from the most recent page of the 1.2.6 beta comments). I'm sure its the same bug:

For some reason, Forge won't open at all. Attempting to open it nets me not one, but two crash reports. [lostinla post end]
This happens to me all the time when I'm developing. It's definitely a pretty annoying bug. Although I know generally the reason it's happening it's hard to pin down exactly why it's happening, so it's not fixed yet. Anyway, duly noted and is definitely going to be squashed at some point.

Makes me think of a fly that you try to smack but it keeps doing that fly-directly-through-your-palm thing and thumbing its nose at you. I've given up for now but it'll bug me again and one of these days - smack! I'll have to wash my hands.

Not sure if this'll hold any water, but the only time I've experienced it is when doing 3d rendering in the background and all 8 cores are being used heavily, so maybe its a threading issue?

Yeah, it's got to do with the controller thinking the view is ready to proceed, when really it's not...there's a thread involved but I haven't chased it down. It's definitely in the interaction between the highest level classes - FControl, FModel, and FView - not a lower level problem.

Most anyone working on the project could have a go at this - I don't think much knowledge of the codebase is needed, there's nothing too crazy, just some time (famous last words) Which bug to attack first, huh?

[squee1968]

Hey Squee,

Was the issue Chris posted in the other thread the issue you are having? What's your specs on your machine? OS, Memory, CPU, the works? I'm considering creating an Ubuntu VM that has the Forge source installed and hooked up to the SVN, this way I can verify everything works. But if you're machine can't handle running a Virtual Machine than it isn't worth it. I know it's not the best solution (I don't know anything about why the Progress Bar would cause issues) but booting a VM to Forge it up, could at least give you something that's functional, if you're computer is able to, and you're willing to give it a shot.

Do the releases work for you either?

Yes, Chris has the correct crash report.

OS: Windows XP Home Edition Version 2002 Service Pack 3
Memory: 2GB RAM
Storage:
Total Memory 2.00 GB
Free Memory 1.07 GB
Total Hard disk 108.59 GB
Free Hard disk 73.63 GB

CPU: Intel Celeron CPU 2.53 GHz
Dell Dimension DE051
Bios: Phoenix ROM BIOS PLUS Version 1.10 A01
Page File: 1216MB Used, 1271MB Available
DirectX: 9.0c (4.09.0000.0904)
Intel 82865G Graphics Controller 96.0 MB
1360 x 768 (32bit) (60Hz)

If you need any more info, just let me know.
I've never used a Virtual Machine before, but I'm willing to try if it will help.
Both the releases and the snapshot builds give the same crash reports, although I note that sometimes the orders are reversed.

[jeffwadsworth]

XP Home...come on man!!

[Sloth]

OS: Windows XP Home Edition Version 2002 Service Pack 3
Memory: 2GB RAM
Storage:
Total Memory 2.00 GB
Free Memory 1.07 GB
Total Hard disk 108.59 GB
Free Hard disk 73.63 GB

CPU: Intel Celeron CPU 2.53 GHz
Dell Dimension DE051
Bios: Phoenix ROM BIOS PLUS Version 1.10 A01
Page File: 1216MB Used, 1271MB Available
DirectX: 9.0c (4.09.0000.0904)
Intel 82865G Graphics Controller 96.0 MB
1360 x 768 (32bit) (60Hz)

If you need any more info, just let me know.

I'm using a similar computer most of the time:

Code: Select all

OS: Windows XP Media Center Edition Version 2002 Service Pack 3
Memory: 2GB RAM
CPU: Intel® Core™ Duo Processor T2300 (2M Cache, 1.66 GHz, 667 MHz FSB)
Graphic: ATI Mobile Radeon X1400 1440 x 900 (32bit)

[timmermac]

XP Home...come on man!!

Hey, now. That's what I'm using too.... until I (hopefully) get my new computer in a couple of months.

[Doublestrike]

This should be fixed now - it was indeed a race condition problem.

[squee1968]

It does appear to be fixed for me (so far). Thanks a ton Doublestrike!