Gamestate Inspector crashes (also with 1.9.13)
Moderator: Forum Moderators
Forum rules
Before reporting issues in this section, you must read the following topic:
Before reporting issues in this section, you must read the following topic:
-
- Posts: 876
- Joined: November 28th, 2008, 6:18 pm
Gamestate Inspector crashes (also with 1.9.13)
The Gamestate Inspector causes Wesnoth to crash if I click on a variable that contains a too long line (123 characters without formatting and indentation was too much)
I recreated the crash with different variables, a long line always implied a crash.
Wesnoth 1.8.5 (english-US)
Widows XP Pro
I recreated the crash with different variables, a long line always implied a crash.
Wesnoth 1.8.5 (english-US)
Widows XP Pro
Last edited by SlowThinker on January 5th, 2012, 11:47 am, edited 1 time in total.
I work on Conquest Minus • I use DFoolWide, Retro Terrain Package and the add-on 'High Contrast Water'
I moved to Nosebane's corner (Doc Paterson's signature); I am spending my time there, so PM me if I don't answer your post in forums
I moved to Nosebane's corner (Doc Paterson's signature); I am spending my time there, so PM me if I don't answer your post in forums
-
- Inactive Developer
- Posts: 2461
- Joined: August 15th, 2008, 8:46 pm
- Location: Germany
Re: Gamestate Inspector crashes if too long line
Doesn't crash in 1.9. Nothing's going to be fixed in 1.8 any more but thx anyway.
Spoiler:
projects (BfW 1.12):
A Simple Campaign: campaign draft for wml starters • Plan Your Advancements: mp mod
The Earth's Gut: sp campaign • Settlers of Wesnoth: mp scenario • Wesnoth Lua Pack: lua tags and utils
updated to 1.8 and handed over: A Gryphon's Tale: sp campaign
A Simple Campaign: campaign draft for wml starters • Plan Your Advancements: mp mod
The Earth's Gut: sp campaign • Settlers of Wesnoth: mp scenario • Wesnoth Lua Pack: lua tags and utils
updated to 1.8 and handed over: A Gryphon's Tale: sp campaign
-
- Posts: 876
- Joined: November 28th, 2008, 6:18 pm
Re: Gamestate Inspector crashes if too long line
With 1.9.13 I can still force the Gamestate Inspector to crash BfW.
And it looks the length of a line is not the problem:
And it looks the length of a line is not the problem:
details
I work on Conquest Minus • I use DFoolWide, Retro Terrain Package and the add-on 'High Contrast Water'
I moved to Nosebane's corner (Doc Paterson's signature); I am spending my time there, so PM me if I don't answer your post in forums
I moved to Nosebane's corner (Doc Paterson's signature); I am spending my time there, so PM me if I don't answer your post in forums
-
- Inactive Developer
- Posts: 2461
- Joined: August 15th, 2008, 8:46 pm
- Location: Germany
Re: Gamestate Inspector crashes (also with 1.9.13)
Again, can't reproduce. This doesn't mean none else can however.
You probably will have to provide more information. Ideally a backtrace. Resolution used or other GUI-related settings can be relevant.
You probably will have to provide more information. Ideally a backtrace. Resolution used or other GUI-related settings can be relevant.
projects (BfW 1.12):
A Simple Campaign: campaign draft for wml starters • Plan Your Advancements: mp mod
The Earth's Gut: sp campaign • Settlers of Wesnoth: mp scenario • Wesnoth Lua Pack: lua tags and utils
updated to 1.8 and handed over: A Gryphon's Tale: sp campaign
A Simple Campaign: campaign draft for wml starters • Plan Your Advancements: mp mod
The Earth's Gut: sp campaign • Settlers of Wesnoth: mp scenario • Wesnoth Lua Pack: lua tags and utils
updated to 1.8 and handed over: A Gryphon's Tale: sp campaign
-
- Posts: 876
- Joined: November 28th, 2008, 6:18 pm
Re: Gamestate Inspector crashes (also with 1.9.13)
I have run several tests.
Operating system: Win XP Pro; 2 GB memory (I just tested it for errors)
BfW had been run in the debug mode with the -d switch.
Sometimes I wasn't able to reproduce the crash even with an identical scenario, but I always found ways how to reproduce it again.
After tests I reported in my last posts, the original scenario and the container 'unit_spawns' still crashed the GI (Gamestate Inspector).
Then I created a tiny scenario "minimum WML code" (it is in the attachment, in a directory 'Scenarios'), that just created the container 'unit_spawns' - and now the GI didn't crash. So a given variable content can cause the crash or not.
Then I removed all scenarios and all add-ons, except the one that crashed before ("full scenario" in the attachment), and it didn't crash now. So a given scenario can cause the crash or not.
Then I returned to the original state of BfW (I moved the addons back) and now the previously 'bad' scenario stopped to crash at all. So a given state of BfW can cause the crash or not.
Most tests were done with the resolution 1600x1144x32. Resolutions 1044x749x32 and
FullScreen (800*600?) usually didn't crash GI.
It appears that a higher chance to a crash cause
Operating system: Win XP Pro; 2 GB memory (I just tested it for errors)
BfW had been run in the debug mode with the -d switch.
Sometimes I wasn't able to reproduce the crash even with an identical scenario, but I always found ways how to reproduce it again.
After tests I reported in my last posts, the original scenario and the container 'unit_spawns' still crashed the GI (Gamestate Inspector).
Then I created a tiny scenario "minimum WML code" (it is in the attachment, in a directory 'Scenarios'), that just created the container 'unit_spawns' - and now the GI didn't crash. So a given variable content can cause the crash or not.
Then I removed all scenarios and all add-ons, except the one that crashed before ("full scenario" in the attachment), and it didn't crash now. So a given scenario can cause the crash or not.
Then I returned to the original state of BfW (I moved the addons back) and now the previously 'bad' scenario stopped to crash at all. So a given state of BfW can cause the crash or not.
Most tests were done with the resolution 1600x1144x32. Resolutions 1044x749x32 and
FullScreen (800*600?) usually didn't crash GI.
It appears that a higher chance to a crash cause
- a higher resolution
- a larger container that is inspected
- more WML installed
- more programs that run in the system besides Wesnoth
- rather "capitol mode" than the simpler "all-villages mode" (maybe because "capitol mode" produces a bit bigger container 'unit_spawns' that crashes the GI)
- Attachments
-
- Conquest-.7z
- In case you want to test: inspect the container 'unit spawns'
- (199.38 KiB) Downloaded 118 times
-
- assertion failure.jpg (24.92 KiB) Viewed 2080 times
I work on Conquest Minus • I use DFoolWide, Retro Terrain Package and the add-on 'High Contrast Water'
I moved to Nosebane's corner (Doc Paterson's signature); I am spending my time there, so PM me if I don't answer your post in forums
I moved to Nosebane's corner (Doc Paterson's signature); I am spending my time there, so PM me if I don't answer your post in forums
-
- Inactive Developer
- Posts: 2461
- Joined: August 15th, 2008, 8:46 pm
- Location: Germany
Re: Gamestate Inspector crashes (also with 1.9.13)
Well, judging from all what you wrote there appears to be a memory problem involved. Crashing sometimes and sometimes not is typical.
A computer has a limited amount of memory and if there's a lot of wml to read then there's some spot when it is used up so it's perhaps not really a bug.
Also, don't be too strict with gui2. It is known to not be the most stable thing.
some related looking reports:
http://gna.org/bugs/index.php?15615
http://gna.org/bugs/index.php?16114
http://gna.org/bugs/index.php?18002
A computer has a limited amount of memory and if there's a lot of wml to read then there's some spot when it is used up so it's perhaps not really a bug.
Also, don't be too strict with gui2. It is known to not be the most stable thing.
some related looking reports:
http://gna.org/bugs/index.php?15615
http://gna.org/bugs/index.php?16114
http://gna.org/bugs/index.php?18002
projects (BfW 1.12):
A Simple Campaign: campaign draft for wml starters • Plan Your Advancements: mp mod
The Earth's Gut: sp campaign • Settlers of Wesnoth: mp scenario • Wesnoth Lua Pack: lua tags and utils
updated to 1.8 and handed over: A Gryphon's Tale: sp campaign
A Simple Campaign: campaign draft for wml starters • Plan Your Advancements: mp mod
The Earth's Gut: sp campaign • Settlers of Wesnoth: mp scenario • Wesnoth Lua Pack: lua tags and utils
updated to 1.8 and handed over: A Gryphon's Tale: sp campaign
-
- Inactive Developer
- Posts: 2461
- Joined: August 15th, 2008, 8:46 pm
- Location: Germany
Re: Gamestate Inspector crashes (also with 1.9.13)
Slow, you may be interested in this one: http://gna.org/bugs/?19283
Which I was able to reproduce with some easy code. The code position of the crash at least is the same.
Which I was able to reproduce with some easy code. The code position of the crash at least is the same.
projects (BfW 1.12):
A Simple Campaign: campaign draft for wml starters • Plan Your Advancements: mp mod
The Earth's Gut: sp campaign • Settlers of Wesnoth: mp scenario • Wesnoth Lua Pack: lua tags and utils
updated to 1.8 and handed over: A Gryphon's Tale: sp campaign
A Simple Campaign: campaign draft for wml starters • Plan Your Advancements: mp mod
The Earth's Gut: sp campaign • Settlers of Wesnoth: mp scenario • Wesnoth Lua Pack: lua tags and utils
updated to 1.8 and handed over: A Gryphon's Tale: sp campaign
-
- Posts: 876
- Joined: November 28th, 2008, 6:18 pm
Re: Gamestate Inspector crashes (also with 1.9.13)
I tested it on my system (1.9.3, Win XP) and the bug was reproduced:
Assertion failed!
File: src/gui/widgets/grid.cpp
Line: 542
Expression: false
The name 'inspect' of your event confused me a bit, I didn't know whether it was not a predefined undocumented event name.
Anyway I fired it by [fire_event].
The bug depended on the resolution of the Wesnoth window: It happened on lower resolutions rather than high ones.
The scroll bar doesn't necessarily cause the bug:
Assertion failed!
File: src/gui/widgets/grid.cpp
Line: 542
Expression: false
The name 'inspect' of your event confused me a bit, I didn't know whether it was not a predefined undocumented event name.
Anyway I fired it by [fire_event].
The bug depended on the resolution of the Wesnoth window: It happened on lower resolutions rather than high ones.
The scroll bar doesn't necessarily cause the bug:
I work on Conquest Minus • I use DFoolWide, Retro Terrain Package and the add-on 'High Contrast Water'
I moved to Nosebane's corner (Doc Paterson's signature); I am spending my time there, so PM me if I don't answer your post in forums
I moved to Nosebane's corner (Doc Paterson's signature); I am spending my time there, so PM me if I don't answer your post in forums