DonationCoder.com Software > Find And Run Robot

FARR crash related to changing monitor sizes.

<< < (2/2)

AJolly:
The crash module is user32.dll, which further implicates farr trying to create a window at an invalid position and not handling the error gracefully.

Faulting application name: FindAndRunRobot.exe, version: 2.239.3.0, time stamp: 0x00000000
Faulting module name: USER32.dll, version: 10.0.22621.2506, time stamp: 0x2f5549b5
Exception code: 0xc000041d
Fault offset: 0x00099825
Faulting process id: 0x0x14F90
Faulting application start time: 0x0x1DA18F1D08F60BB
Faulting application path: C:\ccdc\PortableApps\FindAndRunRobot\FindAndRunRobot.exe
Faulting module path: C:\WINDOWS\System32\USER32.dll
Report Id: 25457af3-6d67-4d34-9402-60c90a4f265d
Faulting package full name:
Faulting package-relative application ID:

AppName = FindAndRunRobot.exe
AppVersion = 2.239.3.0
AppTimeStamp = 00000000
ModuleName = USER32.dll
ModuleVersion = 10.0.22621.2506
ModuleTimeStamp = 2f5549b5
ExceptionCode = c000041d
FaultingOffset = 00099825
ProcessId = 0x14f90
ProcessCreationTime = 0x1da18f1d08f60bb
AppPath = C:\ccdc\PortableApps\FindAndRunRobot\FindAndRunRobot.exe
ModulePath = C:\WINDOWS\System32\USER32.dll
IntegratorReportId = 25457af3-6d67-4d34-9402-60c90a4f265d

Nod5:
I still can't reproduce this issue. If I shut down the FARR process, edit the .ini file, set value MainLeft=4608, and start FARR again it shows up in the middle of the screen. I only have two screens connected. I wonder what else might differ with your PC and screen setup that triggers the issue?

AJolly:
It's very likely the intersection between the ini and your specific screen resolution/ monitor count. 

I've worked around it by writing a batch script that triggers when Windows event log notices process crash, it'll check if farr is running and if not it'll remove that line from the INI and relaunch

mouser:
I apologize for the frustration this must be causing and the creative workarounds you've been willing to create for it!
I will try to fix. 
This seems like a good clue: "1) Farr doesn't actually crash at runtime, it crashes when it's hotkey (alt space) is pressed."
FARR has some code that tries to fix up the window position if it is off screen -- something must be going wrong here.

Quick question first, have you tried changing some of the options that tell FARR whether you want it to automatically position itself on the monitor when it shows?

AJolly:
I've had " When appearing center on monitor turned on", but I'll try disabling it and see if that makes any difference.
The good news is my watchdog script works pretty well.

I do wish far could use some sort of cash to speed up Results though I've been using it for almost 15 years so I don't want to move away, but there's a lot of other launchers these days that run things instantly.

Navigation

[0] Message Index

[*] Previous page