View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0013484 | AI War 1 / Classic | Crash/Exception | Mar 27, 2014 1:59 am | Mar 27, 2014 9:01 pm | |
| Reporter | Chthonic One | Assigned To | keith.lamothe | ||
| Status | assigned | Resolution | open | ||
| Product Version | 7.014 | ||||
| Summary | 0013484: Illegal Address Violation, Fine $300 | ||||
| Description | Random illegal address violation playing with Spelguru. He did not crash, only me. I was host. Save is included (Spelguru was able to save and send it) | ||||
| Tags | No tags attached. | ||||
| Internal Weight | |||||
|
|
|
|
|
One of the logs claims there was 0MB of physical memory and 0MB of pagefile left. But possibly it was just skewed by whatever the real error was. Anyway, we see random crashes like that every now and then and have very little idea what could possibly be causing them (unless it's an out-of-memory situation, and it's not always a scenario big enough as would warrant that). Particularly because all our code is running in the embedded Mono runtime and uses no explicit memory management (pointers), and thus should theoretically be incapable of generating illegal address violations. I'm hoping to upgrade AIW to the latest Unity version to deal with a few things (notably the crash-on-exit on Mac) and perhaps it would help here too, but it's the only thing I can think of that I could actually do to that end. |
|
|
Hrm... I didn't look that far into it, but I do have 16 GB of ram here, and my page file is allowed to increase up to the entire drive size which has 27.5 GB of free space. If it truly ran out, something else had to have cause it to leak most of that memory somewhere. The only thing I was doing at the same time really was watching a stream on twitch.tv on my second monitor. They use Macromedia Flash to encode the player, and that is a notable major memory leaker. However it cannot use more than 2 GB of memory, and it would have crashed as well. |
|
|
Yea, and AIW's process (Mono heap + unmanaged texture memory) can't address more than 2GB either. The nature of the crash probably precluded valid memory reporting. |
|
|
Well, if there is any debugging options you want me to set up for next time me and Spelguru play, perhaps seeing what that says will give me more info to pass onto you for this bug. In the mean time, I enjoy sending you saves showing the insanity that Spelguru causes. Like this time, the 6 counter attacks and normal waves coming in all at the same time. We survived btw, but he keeps me on my toes :D |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Mar 27, 2014 1:59 am | Chthonic One | New Issue | |
| Mar 27, 2014 1:59 am | Chthonic One | File Added: Crash_2014-03-26_213308.zip | |
| Mar 27, 2014 9:34 am | keith.lamothe | Note Added: 0035307 | |
| Mar 27, 2014 9:34 am | keith.lamothe | Assigned To | => keith.lamothe |
| Mar 27, 2014 9:34 am | keith.lamothe | Status | new => assigned |
| Mar 27, 2014 3:08 pm | Chthonic One | Note Added: 0035335 | |
| Mar 27, 2014 8:06 pm | keith.lamothe | Note Added: 0035349 | |
| Mar 27, 2014 9:01 pm | Chthonic One | Note Added: 0035350 | |
| Apr 14, 2014 9:28 am | Chris_McElligottPark | Category | Bug - Crash or Exception => Crash/Exception |
