[11:07:26] <petan>	 phuzion: eh, so what's the issue, new version is crashing and old one isn't?
[11:07:38] <petan>	 how does the crash look, does it report anything, or just segfault?
[11:07:42] <petan>	 can you get trace?
[13:38:22] <phuzion>	 petan: Yeah, new version crashes when reporting to WP:AIV. I can't get a trace, because none of the command line arguments seem to be working for some reason.
[14:34:27] <phuzion>	 I'm trying to reproduce the crash on 3.4.10 on a fresh VM just to make sure it's nothing that's coming from my old installation
[14:51:02] <phuzion>	 Of course when I need to actually report vandals to WP:AIV to test something, they're behaving for once.
[15:02:52] <petan>	 none of the terminal options work? on which os? do they work with previous version?
[15:03:20] <phuzion>	 windows 10 22h2, will test with older versions
[15:04:11] <phuzion>	 3.4.10 and 3.4.11 don't work on win10
[15:04:55] <phuzion>	 And yeah, 3.4.11 still crashes after reporting to WP:AIV on Win10, fresh VM.
[15:04:59] <petan>	 petr.bena@MacBook:~$ /Applications/huggle.app/Contents/MacOS/huggle --version
[15:05:00] <petan>	 Huggle 3.4.11 build: 4100 3.4.11
[15:05:19] <petan>	 on macos it works fine
[15:05:25] <phuzion>	 C:\Program Files\Huggle>huggle.exe --version
[15:05:25] <phuzion>	 C:\Program Files\Huggle>
[15:05:40] <petan>	 hmm yeah I think there was some trick on windows for this
[15:05:51] <petan>	 maybe in powershell it might work
[15:06:13] <petan>	 anyway, I think the options do work, problem is that output to stdout is not visible in windows
[15:06:17] <petan>	 for GUI apps
[15:06:24] <petan>	 windows is redirecting it to some black hole
[15:06:45] <petan>	 try running huggle with higher verbosity like -vvvvvv you should see in logs it's higher
[15:08:08] <phuzion>	 No change with powershell, and adding more v's doesn't force any output.
[15:11:10] <petan>	 no it shouldn't force output, but when you actually open the UI you should see in logs widget that verbosity is increased
[15:12:49] <phuzion>	 ohhhh, gotcha, let me try that.
[15:14:30] <petan>	 this commit must be causing the crashes - https://github.com/huggle/huggle3-qt-lx/commit/17411ba96751267c70a382cbeaef587f52b50db8
[15:15:28] <phuzion>	 Which log widget are you talking about that should show the higher verbosity?
[15:17:14] <petan>	 this is nonsense - https://github.com/huggle/huggle3-qt-lx/blob/master/src/huggle_ui/reportuser.cpp#L328 it's calling this->close() on object that's already deleted
[15:17:32] <petan>	 phuzion: there is "system log" in default UI down there
[15:17:38] <petan>	 showing all sorts of logs
[15:17:54] <phuzion>	 Oh yeah, mine was set to show processes.
[15:18:09] <phuzion>	 And yeah there's a ton of info being shown there.
[15:18:21] <petan>	 if you see green debug lines then -vvvv was processed
[15:18:25] <phuzion>	 Yep
[15:18:26] <petan>	 otherwise there would be no debug lines
[15:18:48] <petan>	 so parser works, just output to console is not visible, but same output goes to this widget
[15:18:54] <petan>	 I think it was same with older versions
[15:19:01] <petan>	 anyway I already found what causes this crash
[15:19:04] <phuzion>	 Oh nice.
[15:19:16] <phuzion>	 3.4.11.1 coming soon? lol
[15:19:30] <petan>	 we dropped that revision bit lol
[15:19:35] <petan>	 so it has to be 3.4.12
[15:21:36] <phuzion>	 Gotcha. Wanna build a 3.4.12 RC and I’ll test it for a day or two and let you know if it works?