Seer failing to start - win10

[ryansean76]

Hi, Seer version 3.2.3 (not MS store version) Plugins: OIT-1.2.0

Recent new user of seer. It has been working perfectly for several days. However it seems like it terminated abnormally yesterday and now will not restart.

No new log information is written to seer.log - renaming the original file before restarting does not result in a new log file being written

The last item opened was a video file - and as far as I could tell usage and termination was normal.

The last [2024/06/26 16:38:29.094] [media] onMediaStarted [2024/06/26 16:38:29.094] [wnd] [timer] elapsed: CMediaWnd(0x1c699af0) 34 ms [2024/06/26 16:38:29.094] [wnd] [load] onLoaded begin [2024/06/26 16:38:29.094] [wnd_ex] afterLoaded [2024/06/26 16:38:29.098] [wnd_ex] resize wnd QRect(2259,548 510x420) [2024/06/26 16:38:29.146] [wnd] [info] load [2024/06/26 16:38:29.150] [wnd] [info] file size "956.13 MiB" [2024/06/26 16:38:29.158] [wnd] [ctrls] control bar update data [2024/06/26 16:38:29.175] [wnd] [load] onLoaded end [2024/06/26 16:38:29.182] [media] isSysMuted 0 [2024/06/26 16:38:29.182] [media] [onMediaPlaying4Ctrls] 25 / 16082024 isSeeking false isSliding false [2024/06/26 16:38:30.280] [wnd_ex] increaseWndSz [2024/06/26 16:38:30.422] [wnd_ex] increaseWndSz [2024/06/26 16:38:30.562] [wnd_ex] increaseWndSz [2024/06/26 16:38:30.707] [wnd_ex] increaseWndSz [2024/06/26 16:38:30.857] [wnd_ex] increaseWndSz [2024/06/26 16:38:36.075] [proc] hash finished with 0 QProcess::NormalExit 7016 ms [2024/06/26 16:38:36.075] [wnd] [load] [plugin] hash received [2024/06/26 16:38:36.076] [wnd] [load] onLoadedFileHash: not plugin "Z:/Downloads/iptv_demo.mp4" [2024/06/26 16:38:36.076] [proc] hash ~ [2024/06/26 16:38:36.076] [proc] hash destroyed 1 ms

I've attached a trace of the the application startup with ProcessMonitor but can't see any obvious reason why the application terminates almost instantly.
[Seer.CSV](https://github.com/user-attachments/files/16011055/Seer.CSV)

Restarting explorer does not change the behavior in anyway. I'm fairly sure that a restart of the PC would solve the problem but I would prefer to not have to resort to that.

[ccseer]

you upgraded Seer from old version to 3.2.3? would you please try to remove the files and install at the same location again?

[ryansean76]

No completely fresh install - I only started using Seer this week. Uninstalled using revo and reinstalled to the same location. Same result I did notice that the folder I installed to was intended for 64 bit applications "Program Files" rather than "Program Files (x86)"- seer is 32 bit I believe.

Let me uninstall again and install to the default location.

[ryansean76]

Same result - I've

1. Reinstalled to the previously selected folder
2. Uninstalled from original location
3. Installed to the default location

Same result in all cases - 5 worker threads shutdown, followed by main thread and process exit. No clear reason as to why. Process monitor output attached if helpful. Seer_install_to_default_location.CSV

[ccseer]

can you try start Seer from command line: Seer.exe -l

On Thu, Jun 27, 2024, 7:10 PM ryansean76 @.***> wrote:

Same result - I've

1. Reinstalled to the previously selected folder
2. Uninstalled from original location
3. Installed to the default location

Same result in all cases - 5 worker threads shutdown, followed by main thread and process exit. No clear reason as to why. Process monitor output attached if helpful. Seer_install_to_default_location.CSV https://github.com/user-attachments/files/16012460/Seer_install_to_default_location.CSV

— Reply to this email directly, view it on GitHub https://github.com/ccseer/Seer/issues/424#issuecomment-2194406068, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADZZIHRIRHRARMZHLI23SELZJPXLBAVCNFSM6AAAAABJ7QKIR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJUGQYDMMBWHA . You are receiving this because you commented.Message ID: @.***>

[ryansean76]

Sure done - no change

[ccseer]

I think I put some dll which are not compatible in the folder

[ryansean76]

Just to update and incase it helps - I restarted the PC in question this morning - and seer returned to working normally.