#2628 closed defect (duplicate)
error while dumping stack: No stack frames found when opening Map editor
| Reported by: | memoconq | Owned by: | |
|---|---|---|---|
| Priority: | Should Have | Milestone: | |
| Component: | Atlas editor | Keywords: | error crash unhandled exception access violation |
| Cc: | Patch: |
Description
I clicked the Map editor icon in the start menu and:
Much to our regret we must report the program has encountered an error.
Please let us know at http://trac.wildfiregames.com/ and attach the crashlog.txt and crashlog.dmp files.
Details: unhandled exception (Access violation reading 0x00000000)
Location: unknown:0 (?)
Call stack:
(error while dumping stack: No stack frames found) errno = 0 (No error reported here) OS error = 0 (no error code was set)
Attachments (4)
Change History (9)
by , 10 years ago
| Attachment: | crashlog.dmp added |
|---|
comment:1 by , 10 years ago
Lenovo W530 with W7 SP1 64
After I clicked continue button, Windows closed the program with following problem details:
Problem signature:
Problem Event Name: APPCRASH Application Name: pyrogenesis.exe Application Version: 0.0.0.0 Application Timestamp: 536fa1c1 Fault Module Name: pyrogenesis.exe Fault Module Version: 0.0.0.0 Fault Module Timestamp: 536fa1c1 Exception Code: c0000005 Exception Offset: 000ce29b OS Version: 6.1.7601.2.1.0.256.4 Locale ID: 1055
follow-up: 4 comment:2 by , 10 years ago
Does this happen every time?
Can we see your system_info.txt? (See GameDataPaths on where to find it)
comment:3 by , 10 years ago
| Milestone: | Backlog |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
follow-up: 5 comment:4 by , 10 years ago
Replying to sanderd17:
Does this happen every time?
Can we see your system_info.txt? (See GameDataPaths on where to find it)
No, I found another way to open the editor. I'm able to open the editor now using the following command:
"D:\0 A.D. alpha\binaries\system\pyrogenesis.exe" -editor
by , 10 years ago
| Attachment: | system_info.txt added |
|---|
comment:5 by , 10 years ago
Replying to memoconq:
No, I found another way to open the editor. I'm able to open the editor now using the following command:
"D:\0 A.D. alpha\binaries\system\pyrogenesis.exe" -editor
Not surprising, the crash had everything to do with timing/scheduling that wasn't fully in the game's control, so making even a small change would be enough to trigger it or prevent it :) Though I'm glad you have a workaround until A17.
dump file