Quote from: Simon on January 17, 2018, 07:39:59 AM
I don't remember the taskbar issue re fullscreen. <_<;; I suppose it wasn't #262 (Fullscreen, can't switch to other windows, Windows)?

I actually meant this issue. I have weird taskbar problems there, that I can't make other windows appear (on old Win 7 laptop) if I have software fullscreen and click on the taskbar after using the Win key .

Description:

Quote
Using the Win key: Clicking on other tabs on the Taskbar doesn't seem to produce visible/overlapping windows (at least for me). But if you use the Start menu as is activated by the Win key (without clicking on the Taskbar beforehand) then it can be possible to produce visible/overlapping windows. If you have produced such a window, even clicking on the Taskbar seems to work in this respect again.

(You can always start other programs (and see them pop up in the Taskbar as tabs), but their windows are not always visible/are sometimes in the background as explained above.)
[...]
The general rule seems to be: Using keys in the first place to get to other windows brings you in a state where you can produce overlapping windows generally (even by clicking on the Taskbar) but using in first place the mouse to click on the Taskbar generally denies you such a state.

But maybe that's something else taskbar related since I think it's been there longer.

Can it be related to the taskbar issue concerning software fullscreen on Win 7? On the Win 8.1 laptop I don't have the fullscreen taskbar issue and the taskbar crash is rare and hard to get. Although Arty has Win 8.0 and consistent crash.

What bugs me is that I don't get an allegro.log. I don't know why.

But nevertheless before fix #222 the crash doesn't seem so likely. Maybe ask Arty if he has the issue with an Lix instance earlier than 0.9.6.

Quote from: Simon on January 17, 2018, 04:12:57 AM
When you ran against debugging libs, did Lix produce allegro.log? Post that if it did.

That's actually the problem that I don't see any. That's why I'm not fully sure if I run against debug libs.
I had an allegro.log as I tried crazy things like putting your dlls with and without -debug in bin but then I think it needed dlls that come with MinGW and it crashed when started with a message from a c++-application.

The error message for the task bar crash always mentions places in allegro code: system.d(45) and system.d(62). Doesn't that mean anything?

Edit: I'm getting more and more the impression that I didn't manage to link against debugging libraries. The only setting where I seemed to have done it, the game refused to run completely (but got allegro.log there).

I think I even tried something like that and it builds and runs but I can't find any log when I get the crash and the error message stays basically the same. (But it looks like I made a debug Allegro build. Not really I just misunderstood something.) Where to find the extra information?

Simon, I'm getting constantly errors that I'm missing DLLs. It started with that allegro-debug-5.2.dll is missing. Can you say which of the countless instances you used (static or dynamic?, i686 or x86_64?, 5.2.3.0 or ~.1?). Do I need MingW?

After several hours of testing around I don't think I can build it without help. I actually don't even know when I successfully build such a build against debugging libraries.

Nevertheless it would be maybe good to have a debugging build against Allegro debug libraries, to see if there is something weird with Allegro.
With this bug I can't be sure of anything, since it is not as clear cut like others. In Win 8.1 I needed countless attempts and fiddling around with the settings to get to the crash, so it's deceiving.
I don't understand enough of the matter to really assess what can cause the bug and what not. So my reduction will generally not to the point.
Up until now we have three settings of the crash: my first crash (0.9.2), task bar (from 0.9.6 on?), double initialization (from 0.9.6 on?). I can't say how connected they are.

Sorry again, but one question: Could it be that fix #222 causes the task bar crash issue?
I reverted the commit in the 0.9.6 source (0.9.6 was the first version where I could reproduce the crash) and it doesn't seem to give me the crash although that doesn't have to mean anything since it is inconsistent for me anyways.

Sorry that I write again, but I think if you open Lix twice at the same time (or maybe a tiny bit delayed?) (e.g. one via link and one via exe) then the error can occur as well.

Just for clarification: Just one of the two instance crashes. I'm not really sure if it is consistent since it's quite fiddly to perform.

Yeah, sorry, I got it now reproduced with Win 8.1 as well, although it's very rare and inconsistent at the moment. (I fiddled around with changing from window to software fullscreen and back but I don't even know if this has anything to do with that.)

Only one addition:
I didn't manage to get the crash on the Win 8.1 laptop, yet. What OS does Arty have?
(Lix 0.9.4. hasn't given me the crash, yet either. Lix 0.9.6 seems to be the first version that gives me the task bar crash.)

I'm not really sure what the conditions for the crash for me are (v. 0.9.8). But some observations (not sure if they are really consistent):

Pattern for the inconsistent crash state:
If I have opened Lix otherwise then close and open from the taskbar I get the error.
If I have the error from the taskbar and open reasonably fast from the taskbar again I generally don't get the error. But if I wait some time (20 sec for example?) the error reoccurs.

Concerning consistent crash state:
Suddenly the error got consistent for me/ it crashes always when I click on the taskbar icon (after waiting time after having the crash but that doesn't cause it always). But I could "fix" it (error has gotten inconsistent again) by removing the link from the taskbar and putting it back on.

Simon, Arty encountered a similiar error when running from the taskbar:

Arty mentioned in IRC:
[23:57:21]    <Arty_> OK. Every time I try to run Lix, I get an error: object.Error@(0): Access Violation. Followed by a bunch of hex numbers
[23:58:28]    <Arty_> Only when I run from the taskbar though

I've tried to reproduce it and it at first didn't give me the crash but now I could reproduce it (It doesn't happen every time but rather often):

The log.txt only says:
Lix version:  0.9.8
Session date: 2018-01-16 01:57:17
     0.06 Allegro 5 can't install audio

I've attached the crash message of the release build and the debug build.

Thanks, Simon, for the quick fix. It seems to work.

I actually actively used (in the older versions) the possibility to view level files in the replay browser in the course of level fixing. In view of that it is very astonishing that I haven't encountered the error earlier. (My replay folder is a bit of a "mine field" now.)

This actually already applied to the 0.9.7 but I've never realized it:
If you put level files in the replay folder and select them from the replay browser the game crashes with Access Violation. In earlier versions there was no problem and it's a bit nasty to have a plain crash just upon selection there.
(This crash happens in the provided binaries as well.)

Full error message (debug build, Win 7):

Lix version:  0.9.8
Session date: 2018-01-15 20:06:35
    30.37 :0:
    30.37 Access Violation
    30.37 0x005105F9 in void menu.browser.replay.BrowserReplay.onFileHighlight(immutable(file.filename.base.IFilename)) at C:\...\LixD-master0_9_8\src\menu\browser\replay.d(82)
0x005112FD in void menu.browser.select.BrowserHighlightSelect.highlight(immutable(file.filename.base.IFilename)) at C:\...\LixD-master0_9_8\src\menu\browser\select.d(58)
0x00511418 in void menu.browser.select.BrowserHighlightSelect.onPickerExecuteFile(immutable(file.filename.base.IFilename)) at C:\...\LixD-master0_9_8\src\menu\browser\select.d(84)
0x0050F32B in D4menu7browser6highli16BrowserHighlight__T6__ctorTC3gui6picker8tilerlev11ReplayTilerZQBrMFxAyay9685BBFB3F63E9BE4E3A4927E21906FF at C:\...\LixD-master0_9_8\src\menu\browser\highli.d(41)
0x004F3A72 in D3gui6pickerQh6Picker__T6__ctorTCQBgQBf8tilerlev11ReplayTilerZQBmMFSQCpQCoQCr__T12PickerConfigT84DD4EB3876DF06FF7B69392533B73CC at C:\...\LixD-master0_9_8\src\gui\picker\picker.d(72)
0x004F6B07 in void gui.picker.tiler.FileTiler.calcSelf() at C:\...\LixD-master0_9_8\src\gui\picker\tiler.d(133)
0x004EB0BC in void gui.element.Element.calc() at C:\...\LixD-master0_9_8\src\gui\element.d(124)
0x004EB407 in void gui.element.Element.calc().__lambda1!(gui.element.Element).__lambda1(gui.element.Element)
0x004EB448 in void std.algorithm.iteration.each!(gui.element.Element.calc().__lambda1).each!(gui.element.Element[]).each(ref gui.element.Element[]) at C:\D\dmd2\windows\bin\..\..\src\phobos\std\algorithm\iteration.d(944)
0x004EB0B4 in void gui.element.Element.calc() at C:\...\LixD-master0_9_8\src\gui\element.d(123)
0x004EB407 in void gui.element.Element.calc().__lambda1!(gui.element.Element).__lambda1(gui.element.Element)
0x004EB448 in void std.algorithm.iteration.each!(gui.element.Element.calc().__lambda1).each!(gui.element.Element[]).each(ref gui.element.Element[]) at C:\D\dmd2\windows\bin\..\..\src\phobos\std\algorithm\iteration.d(944)
0x004EB0B4 in void gui.element.Element.calc() at C:\...\LixD-master0_9_8\src\gui\element.d(123)
0x004EB407 in void gui.element.Element.calc().__lambda1!(gui.element.Element).__lambda1(gui.element.Element)
0x004EB448 in void std.algorithm.iteration.each!(gui.element.Element.calc().__lambda1).each!(gui.element.Element[]).each(ref gui.element.Element[]) at C:\D\dmd2\windows\bin\..\..\src\phobos\std\algorithm\iteration.d(944)
0x004EB0B4 in void gui.element.Element.calc() at C:\...\LixD-master0_9_8\src\gui\element.d(123)
0x004F96E6 in void gui.root.calc() at C:\...\LixD-master0_9_8\src\gui\root.d(96)
0x00428C2F in void basics.mainloop.MainLoop.calc() at C:\...\LixD-master0_9_8\src\basics\mainloop.d(159)
0x0042898B in void basics.mainloop.MainLoop.mainLoop() at C:\...\LixD-master0_9_8\src\basics\mainloop.d(82)
0x0050E540 in int main.main(immutable(char)[][]).__lambda2() at C:\...\LixD-master0_9_8\src\main.d(39)
0x00530453 in extern (C) int allegro5.system.al_run_allegro(scope int delegate()).main_runner(int, char**) at C:\Users\...\AppData\Roaming\dub\packages\allegro-4.0.1_5.2.0\allegro\allegro5\system.d(45)
0x00530437 in int allegro5.system.al_run_allegro(scope int delegate()) at C:\Users\...\AppData\Roaming\dub\packages\allegro-4.0.1_5.2.0\allegro\allegro5\system.d(62)
0x0050E4F3 in _Dmain at C:\...\LixD-master0_9_8\src\main.d(35)
0x0053D933 in void rt.dmain2._d_run_main(int, char**, extern (C) int function(char[][])*).runAll().__lambda1()
0x0053D8F7 in void rt.dmain2._d_run_main(int, char**, extern (C) int function(char[][])*).runAll()
0x0053D7F8 in _d_run_main
0x0050E56C in main at C:\...\LixD-master0_9_8\src\verify\counter.d(7)
0x0057C119 in mainCRTStartup
0x7660337A in BaseThreadInitThunk
0x77C19882 in RtlInitializeExceptionChain
0x77C19855 in RtlInitializeExceptionChain