Skip to content
View in the app

A better way to browse. Learn more.

W3D Hub

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Launcher crashing after update

Featured Replies

Had the launcher update today (somewhere around 900 kb) and after updating every time I would try to switch to the Server Browser tab it instantly stopped responding and had to be force closed.  Rebooted, same problem persisted.  It seems to be working alright now after about the 5th or 6th attempt, but I figured I'd still send the report in case others are also having this issue.

If any other info about my system is needed git at me!

DxDiag.txt

diagnostics.log

errors.log

Edited by akhero47

I am by no means an expert on the launcher, and its pretty likely that danpaul is the only one that can say for sure what caused this, but I like to poke around and stab in the dark and see what I can learn :p So tell me, did you run as admin or otherwise grant it admin access in a UAC prompt? Because (this is a pure guess) it seems like these two lines refer to the actual ability of the application to start and do anything at all.

at System.Windows.Application.Run()
at W3DHub.Launcher.App.Main()

If the program failed on these (along with the few dozen other errors) then the PC tech in me screams "perms". There are some funky situations in windows where apps can attempt to run but any elevation prompts will be suppressed or denied by default, even if you right click and run as admin! It can silently deny it. Just a guess again, but I would think that could cause an error of this sort. Why that would happen but then not happen later, and the program be allowed to run normally is beyond me though, unless you changed some security settings.

Do you by chance have an "over-zealous" antivirus? :p

@Einstein actually those two lines just mean it's on thread 1, the main application thread.

I'm on my phone right now so can't load up the code to have a poke around, but it's not one I've seen during my own testing. It looks like a threading issues where a UI update is happening outside the UI thread, but where and when it's happening isn't clear.

I'll have a look when I'm next on my laptop, but it smells like one of those that will be hard to track down...

  • Author
17 hours ago, Einstein said:

I am by no means an expert on the launcher, and its pretty likely that danpaul is the only one that can say for sure what caused this, but I like to poke around and stab in the dark and see what I can learn :p So tell me, did you run as admin or otherwise grant it admin access in a UAC prompt? Because (this is a pure guess) it seems like these two lines refer to the actual ability of the application to start and do anything at all.

at System.Windows.Application.Run()
at W3DHub.Launcher.App.Main()

If the program failed on these (along with the few dozen other errors) then the PC tech in me screams "perms". There are some funky situations in windows where apps can attempt to run but any elevation prompts will be suppressed or denied by default, even if you right click and run as admin! It can silently deny it. Just a guess again, but I would think that could cause an error of this sort. Why that would happen but then not happen later, and the program be allowed to run normally is beyond me though, unless you changed some security settings.

Do you by chance have an "over-zealous" antivirus? :p

Yep, tried running as admin after the first two tries.  No effect.

It can be, but I don't think it was the problem as usually if it's causing an interruption in a program functioning properly it tells me something along the lines of "Hey!  We think you're really stupid for opening or executing this!  Don't do it!  Or..  do but don't say we didn't tell you so!"

 

Edit:  Like I said, it's working fine now with me having done no changes whatsoever to anything.  I just worry maybe someone else could have the same issue and not have it self-repair.

Edited by akhero47

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.