搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

xul runner pop-up: "could not determine any profile running in backgroundtask mode"

  • 1 回覆
  • 2 有這個問題
  • 10 次檢視
  • 最近回覆由 5crambler

more options

After booting up my PC and logging in to Win10 I get a pop-up window (see attached 1) although I haven't even started FF.

The only FF process running during boot/login is the background update (see attached 2), but this never showed such a message before. I've been using FF for ages.

FF was updating successfully to 98.0.1 yesterday before I shut down my PC. FF seems to keep working with no problem - I'm using it right now...

I recently installed ExpressVPN which blocks internet access until the tunnel is established. So maybe the background update process got confused because it couldn't access the internet?

Any other ideas why I got this message - or how to get rid of it?


11am (my time): Background Update ran again (attached 3) with result code 0x15 (1st run was 0x0) but did not show any message this time...

After booting up my PC and logging in to Win10 I get a pop-up window (see attached 1) although I haven't even started FF. The only FF process running during boot/login is the background update (see attached 2), but this never showed such a message before. I've been using FF for ages. FF was updating successfully to 98.0.1 yesterday before I shut down my PC. FF seems to keep working with no problem - I'm using it right now... I recently installed ExpressVPN which blocks internet access until the tunnel is established. So maybe the background update process got confused because it couldn't access the internet? Any other ideas why I got this message - or how to get rid of it? ------ 11am (my time): Background Update ran again (attached 3) with result code 0x15 (1st run was 0x0) but did not show any message this time...
附加的畫面擷圖

由 5crambler 於 修改

所有回覆 (1)

more options

code section producing the message (mozilla-central/toolkit/xre/nsAppRunner.cpp) commented "We should never get to this point in background task mode"

[...]

/**

* This class, instead of a raw nsresult, should be the return type of any
* function called by SelectProfile that initializes XPCOM.
*/

class ReturnAbortOnError {

public:
 MOZ_IMPLICIT ReturnAbortOnError(nsresult aRv) { mRv = ConvertRv(aRv); }
 operator nsresult() { return mRv; }
private:
 inline nsresult ConvertRv(nsresult aRv) {
   if (NS_SUCCEEDED(aRv) || aRv == NS_ERROR_LAUNCHED_CHILD_PROCESS) {
     return aRv;
   }
  1. ifdef MOZ_BACKGROUNDTASKS
   // A background task that fails to lock its profile will return
   // NS_ERROR_UNEXPECTED and this will allow the task to exit with a
   // non-zero exit code.
   if (aRv == NS_ERROR_UNEXPECTED && BackgroundTasks::IsBackgroundTaskMode()) {
     return aRv;
   }
  1. endif
   return NS_ERROR_ABORT;
 }
 nsresult mRv;

};

} // namespace

static nsresult ProfileMissingDialog(nsINativeAppSupport* aNative) {

  1. ifdef MOZ_BACKGROUNDTASKS
 if (BackgroundTasks::IsBackgroundTaskMode()) {
   // We should never get to this point in background task mode.
   Output(false,
          "Could not determine any profile running in backgroundtask mode!\n");
   return NS_ERROR_ABORT;
 }
  1. endif

[...]