Gimx application Crashes

Need help? Ask here and someone will help
redion1992
Posts: 15
Joined: Wed Dec 13, 2017 3:19 pm

Re: Gimx application Crashes

Post by redion1992 » Sat Dec 30, 2017 1:09 pm

Well, I just did a clean reinstall. Wiped everything on the SSD, and started from scratch... and I'm still having issues. I do wonder if some of the less common software I run could be causing an issue, most notably a thing called DrivePool (which basically acts as an overlay RAID on top of an NTFS filesystem), which is not something I can easily disable. Another tweak I made is changing the default COM port using the driver software, as I already have some ports in use for other devices. However, it all matches up in GIMX to the port I selected.

Regarding remote access, when would work for you? I'm currently in GMT+11.

User avatar
Matlo
Posts: 4812
Joined: Wed Jul 06, 2011 7:01 am
Location: France
Contact:

Re: Gimx application Crashes

Post by Matlo » Sun Dec 31, 2017 9:43 am

Before doing any remote debugging, please explain the current state. Does it still crash? If yes, could you provide another crash dump? Otherwise, could you provide a log file?
GIMX creator Donate Shop

redion1992
Posts: 15
Joined: Wed Dec 13, 2017 3:19 pm

Re: Gimx application Crashes

Post by redion1992 » Sun Dec 31, 2017 10:04 am

Just tested it again. This time, the only displayed text in the GIMX console window is:

Code: Select all

windows/gprio.c:23 gprio: failed to set priority class
ProcDump gave the following output:

Code: Select all

Process:               gimx.exe (3620)
Process image:         C:\Program Files\GIMX\gimx.exe
CPU threshold:         n/a
Performance counter:   n/a
Commit threshold:      n/a
Threshold seconds:     n/a
Hung window check:     Disabled
Log debug strings:     Disabled
Exception monitor:     Unhandled
Exception filter:      [Includes]
                       *
                       [Excludes]
Terminate monitor:     Disabled
Cloning type:          Disabled
Concurrent limit:      n/a
Avoid outage:          n/a
Number of dumps:       1
Dump folder:           D:\Applets\ProcDump\
Dump filename/mask:    PROCESSNAME_YYMMDD_HHMMSS
Queue to WER:          Disabled
Kill after dump:       Disabled


Press Ctrl-C to end monitoring without terminating the process.

[20:57:16] Exception: 80000003.BREAKPOINT
[20:57:16] Exception: C0000374
[20:57:16] Unhandled: C0000374
[20:57:16] Dump 1 initiated: D:\Applets\ProcDump\gimx.exe_171231_205716.dmp
[20:57:16] Dump 1 writing: Estimated dump file size is 92 MB.
[20:57:17] Dump 1 complete: 93 MB written in 0.8 seconds
[20:57:17] Dump count reached.
Dump download linked here. This was generated using GIMX 6.11 (last stable).

I also got a log file out of it, however none of it showed in the console:

Code: Select all

global option -l with value `log.txt'
global option -c with value `LogitechG27_G29.xml'
controller #1: option -p with value `COM11'
now reading arguments for controller #2
status flag is set
subpos flag is set
force_updates flag is set
GIMX 6.11 x86_64
Windows 10 (or later) x64
Kernel version: 10.0 (16299)
USB adapter detected, controller type is: G29 PS4.
found pass-through device 0x054c:0x09cc
Timer resolution: min=156250 max=5000 current=5007
using default refresh period: 5.00ms
mouse 0 has name 'HID-compliant mouse' and virtual id 0
mouse 1 has name 'HID-compliant mouse' and virtual id 1
mouse 2 has name 'HID-compliant mouse' and virtual id 2
mouse 3 has name 'HID-compliant mouse' and virtual id 3
mouse 4 has name 'HID-compliant mouse' and virtual id 4
mouse 5 has name 'HID-compliant mouse' and virtual id 5
mouse 6 has name 'HID-compliant mouse' and virtual id 6
mouse 7 has name 'Razer Tartarus Chroma' and virtual id 0
mouse 8 has name 'HID-compliant mouse' and virtual id 7
joystick 0 has name 'PS4 Controller' and virtual id 0
joystick 1 has name 'Razer Tartarus Chroma' and virtual id 0
joystick 2 has name 'Logitech G27 Racing Wheel USB' and virtual id 0
macros are not available for: joystick PS4 Controller (0)
Warning: can't open macro directory C:\Users\David\AppData\Roaming//gimx//macros/
FFB device: Logitech G27 Racing Wheel USB 0 (direct translation).
Press the PS button to activate the controller.
0 1514714237.341025, wheel (153)

User avatar
Matlo
Posts: 4812
Joined: Wed Jul 06, 2011 7:01 am
Location: France
Contact:

Re: Gimx application Crashes

Post by Matlo » Sun Dec 31, 2017 10:12 am

Could you please try with the GIMX 7.0 beta?

https://gimx.fr/download/2a7c5e3baff947 ... x86_64.exe
GIMX creator Donate Shop

redion1992
Posts: 15
Joined: Wed Dec 13, 2017 3:19 pm

Re: Gimx application Crashes

Post by redion1992 » Sun Dec 31, 2017 10:18 am

I'm finding I have to reboot between each attempt, otherwise something goes wrong and I keep getting an error from ProcDump after the first run. And unfortunatley, on that run just then, not only did GIMX crash, but so did ProcDump without capturing anything! Upgraded the installed version to 7.0 beta, but I'll try again in a moment.

redion1992
Posts: 15
Joined: Wed Dec 13, 2017 3:19 pm

Re: Gimx application Crashes

Post by redion1992 » Sun Dec 31, 2017 10:29 am

OK, 7.0 beta logs:

GIMX Console:

Code: Select all

src/windows/gprio.c:23 gprio: failed to set priority class
GIMX logfile:

Code: Select all

global option -l with value `log.txt'
global option -c with value `LogitechG27_G29.xml'
controller #1: option -p with value `COM11'
now reading arguments for controller #2
status flag is set
subpos flag is set
force_updates flag is set
GIMX 7.0 x86_64
Windows 10 (or later) x64
Kernel version: 10.0 (16299)
GIMX adapter detected, controller type is: G29 PS4.
found pass-through device 0x054c:0x09cc
Timer resolution: min=156250 max=5000 current=5007
registered joystick 0 with name "PS4 Controller"
using default refresh period: 5.00ms
mouse 0 has name 'HID-compliant mouse' and virtual id 0
mouse 1 has name 'HID-compliant mouse' and virtual id 1
mouse 2 has name 'HID-compliant mouse' and virtual id 2
mouse 3 has name 'HID-compliant mouse' and virtual id 3
mouse 4 has name 'HID-compliant mouse' and virtual id 4
mouse 5 has name 'HID-compliant mouse' and virtual id 5
mouse 6 has name 'HID-compliant mouse' and virtual id 6
mouse 7 has name 'HID-compliant mouse' and virtual id 7
mouse 8 has name 'Razer Tartarus Chroma' and virtual id 0
joystick 0 has name 'PS4 Controller' and virtual id 0
joystick 1 has name 'Razer Tartarus Chroma' and virtual id 0
joystick 2 has name 'Logitech G27 Racing Wheel USB' and virtual id 0
Warning: macros are not available for: joystick PS4 Controller (0)
Warning: can't open macro directory C:\Users\David\AppData\Roaming//gimx//macros/
Haptic core has source haptic_source_lg for device 046d:c24f
Haptic core has sink haptic_sink_os for joystick 2 (Logitech G27 Racing Wheel USB)
FFB invert: no
FFB gain: constant=100 spring=100 damper=100
Press the PS button to activate the controller.
0 1514715789.211166
ProcDump log (dump download)

Code: Select all

Waiting for process named gimx.exe...

Process:               gimx.exe (20056)
Process image:         C:\Program Files\GIMX\gimx.exe
CPU threshold:         n/a
Performance counter:   n/a
Commit threshold:      n/a
Threshold seconds:     n/a
Hung window check:     Disabled
Log debug strings:     Disabled
Exception monitor:     Unhandled
Exception filter:      [Includes]
                       *
                       [Excludes]
Terminate monitor:     Disabled
Cloning type:          Disabled
Concurrent limit:      n/a
Avoid outage:          n/a
Number of dumps:       1
Dump folder:           D:\applets\ProcDump\
Dump filename/mask:    PROCESSNAME_YYMMDD_HHMMSS
Queue to WER:          Disabled
Kill after dump:       Disabled


Press Ctrl-C to end monitoring without terminating the process.

[21:23:08] Exception: 80000003.BREAKPOINT
[21:23:08] Exception: C0000374
[21:23:08] Unhandled: C0000374
[21:23:08] Dump 1 initiated: D:\applets\ProcDump\gimx.exe_171231_212308.dmp
[21:23:08] Dump 1 writing: Estimated dump file size is 77 MB.
[21:23:08] Dump 1 complete: 77 MB written in 0.6 seconds
[21:23:09] Dump count reached.
Very similar to the previous version, slight changes to the console log but the exceptions are still the same.

User avatar
Matlo
Posts: 4812
Joined: Wed Jul 06, 2011 7:01 am
Location: France
Contact:

Re: Gimx application Crashes

Post by Matlo » Sun Dec 31, 2017 12:22 pm

Thanks. I will make another fix attempt and build a new beta version.
GIMX creator Donate Shop

redion1992
Posts: 15
Joined: Wed Dec 13, 2017 3:19 pm

Re: Gimx application Crashes

Post by redion1992 » Sun Dec 31, 2017 1:46 pm

I have a bit of a hunch based on some experiments. Using some of the command line options for GIMX, I've found that it crashes when referring to a configuration XML. This also occurs when hitting Check in Gimx-launcher, and I'm assuming that when starting Gimx-config from the launcher it tries to automatically open the config file as well, and that crashes. Looking at line 1533 of launcher/gimx-launcher.cpp, that's the function that appears to be called when checking the configuration. I removed all configs, restarted the launcher, and clicked Check, and the IsEmpty() function part ran correctly, without crashing. But if there is a config file selected, it crashes before showing any message box, meaning it's dying somewhere between lines 1541 and 1545 of that source file. Unfortunately, I can't seem to figure out how to build a debug version to step through on Windows (setting up Eclipse and wxWidgets and all that), otherwise I'd take a look at it myself.

User avatar
Matlo
Posts: 4812
Joined: Wed Jul 06, 2011 7:01 am
Location: France
Contact:

Re: Gimx application Crashes

Post by Matlo » Sun Jan 07, 2018 9:57 pm

Happy new year! Let's hope we can fix this in 2018 :)

I made a new beta version: https://gimx.fr/download/7a29b9ead9b069 ... 0-i386.exe

This time it is a 32-bit version. This allows to use drmemory to get runtime memory analysis.
You can download it here: https://github.com/DynamoRIO/drmemory/r ... 11.0-2.msi

You will find a drmemory.bat file in the GIMX install dir - default is C:\Program Files (x86)\GIMX . Just run it and it will start gimx.exe with drmemory and the default argument values stored on disk by gimx-launcher (they are only saved on successful run, you can adjust them as needed). Please let me know if this version still crashes, and in case it does, please send me a drmemory report.
GIMX creator Donate Shop

redion1992
Posts: 15
Joined: Wed Dec 13, 2017 3:19 pm

Re: Gimx application Crashes

Post by redion1992 » Mon Jan 08, 2018 5:31 am

Just tested it. Crashed again. I had to edit the drmemory.bat, as I don't have a user account named Matlo on my PC :P And it turns out that it doesn't like to run the x86 version of Dr. Memory on an x64 PC. It threw the following message:

Code: Select all

~~Dr.M~~ Running on an unsupported operating system. Please download http://drmemory.org/syscalls_wow64.txt and save as C:\Program Files (x86)\Dr. Memory\bin\syscalls_wow64.txt to avoid false positives and other problems. If that fails, please file a bug report. Re-run with -ignore_kernel to attempt continued execution.
Once that was completed (the file download, not editing to run with -ignore-kernel), I ran it again. Here's the output.

Also, just a note - you left the x64 versions of the CP210x drivers and UsbDk included in that package, not sure if that was intentional or not (given that this version was an x86 build, I'm not directly sure if they're compatible).

Post Reply