There has been a few reports of random crashing in the Office.
Normally this occurs when loading the office or doing something in the office that involves processing.
In the logfile.log there is no visible errors...
I believe this is an
buffer overflow error, an issue with the audio playback system, or both. It may take a while to find it...
If you run into a random crash in the office please upload your log files to this thread.
Thank you and sorry for the inconvenience.
I run into this problem: I selected Office->Reports log->Expenses and it crashed
I hope the log is useful, because I opened the game again, the next time I will first insert here the log
In my case is always crash when i try to open some charts.
Seems like the office is acting up again...
After starting my 3rd game, entering expenses causes a crash.
Restarted 3 times, still crashes when entering expenses. See attached log.
It crashed as I pushed... something (can't remember), but it was in the office. It's the same as the globe incident I reported earlier.
(10-11-2013, 03:38 PM)WaterlandBaits Wrote: [ -> ]After starting my 3rd game, entering expenses causes a crash.
Restarted 3 times, still crashes when entering expenses. See attached log.
Could you attach the saved game for me? It is located in the same directory as the log file. You will need to zip or rar the file before uploading it to the forums.
I believe this issue has been fixed for 1.09. It should be crashes if you look at the expenses while you are designing a gearbox. Once the gearbox is finished being design it should work fine again.
I would like to check it though just to be sure.
(10-11-2013, 06:38 PM)ChaapaNA Wrote: [ -> ]It crashed as I pushed... something (can't remember), but it was in the office. It's the same as the globe incident I reported earlier.
I believe this is the same issue as the other ones, vram or video card issue. Once 1.09 comes out if you still have this issue we'll go from there.
(10-11-2013, 10:29 PM)Eric.B Wrote: [ -> ]Could you attach the saved game for me? It is located in the same directory as the log file. You will need to zip or rar the file before uploading it to the forums.
I believe this issue has been fixed for 1.09. It should be crashes if you look at the expenses while you are designing a gearbox. Once the gearbox is finished being design it should work fine again.
I would like to check it though just to be sure.
Yup, true! After trying to restart the game several times, i got tired and reinstalled the game. So save is deleted. However, thx for the tip!
Crash when I tried to access the newspaper.
(11-21-2013, 05:19 PM)Giacomo Wrote: [ -> ]Crash when I tried to access the newspaper.
Your bug has been fixed, and will be included in the 1.10 release.
This does not pertain to the random office crashing issue.
First time with me.
Clicked on the R&D button within the office page and the game crashed.
Logfile included.
Was in R&D. Had spent some time designing a chassis, engine and gearbox. When I pressed the button to return to the office, the program crashed. Attaching the log file.
Crash when I pressed the end turn button (via the grandfather clock)
Logfile attached
I've merged three of your threads into this one Giacomo, as they all come from the same issue. The game is overflowing the stack when allocating memory for the office GUI. When I get the Linux build up and running I'll run Valgrind and hopefully fix some of these issues! Till then its a crap shoot if I can find the issue or not.
Pressing F12 in the office, after several retool and factory closes.
Seems like another case of the office memory leak!
Hopefully when I can afford another computer, I can get slackware up and running on it and use valgrind to fix it.
In the mean time try to save after about an hour of play on your box because you'll have a slight chance of crashing out.
Started new hard game after being unable to load last hard game. Designed a chassis, gearbox and engine then returned to office to advance turn and game crashed.
Heres the log file
I assume the game worked fine after that. I believe this is the same Memory Leak issue that has been plaguing us in the office for a while.
I should be able to catch it when I run valgrind on the program later this year.