Messages - AJolly [ switch to compact view ]

Pages: [1] 2 3 4 5 • next
1
Find And Run Robot / Re: FARR crash related to changing monitor sizes.
« on: January 16, 2024, 01:18 PM »
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.

2
Find And Run Robot / Re: FARR crash related to changing monitor sizes.
« on: November 26, 2023, 04:21 PM »
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

3
Find And Run Robot / Re: FARR crash related to changing monitor sizes.
« on: November 16, 2023, 07:13 PM »
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

4
Find And Run Robot / Re: FARR crash related to changing monitor sizes.
« on: November 16, 2023, 07:11 PM »
I think I've diagnosed the root of the problem:
Farr crashes on activation if the saved position of it's window is no longer valid.  This can happen without having negative numbers. 
1) Farr doesn't actually crash at runtime, it crashes when it's hotkey (alt space) is pressed.
2) Deleting the window position info in the ini lets farr run fine.

Example: Today I swapped monitors (I have 5 monitors connected to my pc, by flipping a power switch I move between using 3 at my desk vs 2 at my couch).  Tried launching farr, nothing happened.  In the ini, there were no negative position numbers.  Removed the MainLeft number, reran farr and it works fine. 

[Windows]
MainLeft=4608
MainTop=1173
MainWidth=2304
MainHeight=767
OptionsLeft=1
OptionsTop=109
OptionsWidth=1142
OptionsHeight=815
AliasLeft=1
AliasTop=108
AliasWidth=958
AliasHeight=662
OptionsActivePage=4
OptionsTransparency=0
ToolbarWidth=90
PluginManagerWidth=958
PluginManagerHeight=843
HotkeyFormWidth=629
HotkeyFormHeight=522
CheckBoxUseCustomBackgroundResultColor=0
ColorBoxCustomBackground=-16777201
CheckBoxUseCustomBackgroundSearchColor=0
ColorBoxCustomSearchBackground=-16777201
ResultMode_Width_0=-1
ResultMode_Height_0=-1
ResultMode_Width_1=1044
ResultMode_Height_1=658
ResultMode_Width_2=2304
ResultMode_Height_2=139
ResultMode_Width_3=2304
ResultMode_Height_3=767
ResultMode_Width_4=-1
ResultMode_Height_4=-1
ResultMode_Width_5=-1
ResultMode_Height_5=-1
ResultMode_Width_6=-1
ResultMode_Height_6=-1

5
Find And Run Robot / Re: FARR crash related to changing monitor sizes.
« on: November 06, 2023, 05:34 AM »
That's the weird thing, I've now had this happen to me across two different computers, multiple times. At some point I'll notice that farr is no longer running, try and restart it and realize it's not starting.  Go delete that section in the ini, and it works just fine again. 

I've got some of the crash dumps if that helps.  I've been using farr for a decade now, but this is the first time I've been switching between monitors so frequently.

I guess I'll try putting back in that section next time it crashes, or let me try and figure out some sort of watchdog script so I get notified when farr crashes. 

Pages: [1] 2 3 4 5 • next
Go to full version