New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 791343 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

chrome.alarms.create: Uncaught RangeError: Unsupported time zone specified undefined

Reported by ilyaigpe...@gmail.com, Dec 3 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/62.0.3202.94 Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
1. On linux wake up run the code:
```
chrome.alarms.create(
  this._periodicUpdateAlarmReason, // plain string
  {
    when: nextUpdateMoment, // integer, milliseconds
    periodInMinutes: this._pacUpdatePeriodInMinutes, // integer
  }
);

```
Except comments this code is taken verbatim from the extension that thrown this exception.

What is the expected behavior?
no error

What went wrong?
Time zone can't be specified in `chrome.alarms.create` API, it means this error is internal to chrome.

Full error report by extension was also added to this report below.

I doubt extension source codes may help, but here are they too:
https://github.com/anticensority/chromium-extension/blob/0972bf106f03d744a84591ff56e790bd2a12da8e/extensions/chromium/runet-censorship-bypass/src/extension-common/37-sync-pac-script-with-pac-provider-api.tmpl.js

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 62.0.3202.94  Channel: stable
OS Version: 
Flash Version: 

{
  "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/62.0.3202.94 Chrome/62.0.3202.94 Safari/537.36",
  "platform": "Linux x86_64",
  "version": "0.0.1.16",
  "ext-error": {
    "message": "Uncaught RangeError: Unsupported time zone specified undefined",
    "filename": "chrome-extension://npgcnondjocldhldegnakemclmfkngch/37-sync-pac-script-with-pac-provider-api.js",
    "lineno": 392,
    "colno": 36,
    "error": {
      "stack": "RangeError: Unsupported time zone specified undefined\n    at new DateTimeFormat (native)\n    at Date.toLocaleString (native)\n    at Object.setAlarms (chrome-extension://npgcnondjocldhldegnakemclmfkngch/37-sync-pac-script-with-pac-provider-api.js:392:36)\n    at window.addEventListener (chrome-extension://npgcnondjocldhldegnakemclmfkngch/37-sync-pac-script-with-pac-provider-api.js:479:20)",
      "message": "Unsupported time zone specified undefined",
      "name": "RangeError"
    },
    "type": "error"
  }
}
 
I attach extension source file in which error was thrown in case our extension will be removed from GitHub.
37-sync-pac-script-with-pac-provider-api.tmpl.js
15.8 KB View Download
On windows 10 Wake up from sleep.

Chrome version: 62.0.3202.94 (Официальная сборка), (64 бит)
OS Version: Windows10 x64 1709 16299.64

{
  "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36",
  "platform": "Win32",
  "version": "0.0.1.16",
  "ext-error": {
    "message": "Uncaught RangeError: Unsupported time zone specified undefined",
    "filename": "chrome-extension://npgcnondjocldhldegnakemclmfkngch/37-sync-pac-script-with-pac-provider-api.js",
    "lineno": 392,
    "colno": 36,
    "error": {
      "stack": "RangeError: Unsupported time zone specified undefined\n    at new DateTimeFormat (native)\n    at Date.toLocaleString (native)\n    at Object.setAlarms (chrome-extension://npgcnondjocldhldegnakemclmfkngch/37-sync-pac-script-with-pac-provider-api.js:392:36)\n    at window.addEventListener (chrome-extension://npgcnondjocldhldegnakemclmfkngch/37-sync-pac-script-with-pac-provider-api.js:479:20)",
      "message": "Unsupported time zone specified undefined",
      "name": "RangeError"
    },
    "type": "error"
  }
}
Sorry, maxxto... is correct, on Windows, error happened on his machine. I'm the developer of the extension on which it happened and my error report must be replaced with his above.
Cc: krajshree@chromium.org
Components: Platform>Extensions
Labels: Needs-Triage-M62 Needs-Feedback Triaged-ET
ilyaigpetrov@ - Thanks for filing the issue...!!

Tried testing the issue by downloading code from the url: https://github.com/anticensority/chromium-extension/blob/0972bf106f03d744a84591ff56e790bd2a12da8e/extensions/chromium/runet-censorship-bypass/src/extension-common/37-sync-pac-script-with-pac-provider-api.tmpl.js
but unable to add the extension to chrome://extensions.

Could you please provide a sample extension file to test the issue from TE-end. Also if possible please provide a screenshot explaining the issue exactly.
This will help us in triaging the issue further.

Thanks...!!
Hi, krajshree@. I was trying to reproduce this bug with a minimal test case, but it didn't work. However code owner still could find it out what's wrong from the error message and fix it.

The only testing we have -- is on the whole extension https://rebrand.ly/ac-webstore. If you are going to test on whole extension, please, ask  maxxto...@gmail.com for actual steps to reproduce the issue.

Thanks for you help.
Project Member

Comment 6 by sheriffbot@chromium.org, Dec 4 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Steps to reproduce the problem:
Install extension https://rebrand.ly/ac-webstore
Transfer PC to sleep mode
Wake it up
When the browser window is active, we get an error
2017-12-05 00-07-39 Скриншот экрана.png
96.3 KB View Download
Labels: TE-NeedsTriageFromHYD
Unable to reproduce the issue on Win-10 using chrome reported version #62.0.3202.94.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Install extension https://rebrand.ly/ac-webstore
2. Transferred pc to sleep mode
3. Woke it up after 5 min.
4. Observed that when the browser window was active, no error was observed.

As the issue is seen on Linux PC and ET team doesn't have the device. Hence, forwarding to inhouse team to have a look into the issue.

Thanks...!!

Comment 9 by hdodda@chromium.org, Dec 11 2017

Cc: hdodda@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issu eon ubuntu 14.04 , Mac OS 10.12.6 and windows 7 & 10 using chrome latest stable M63 #63.0.3239.84 and M65 #65.0.3291.0

Followed the steps mentioned in comment #8 and not able to see any error after wakeup.

@ ilyaigpetrov-- Could you please confirm us if you can still see the issue on latest stable and update us with your observations.

Thanks!
I confirm - the bug disappeared. On two machines Windows 10 Pro (Version 1709, Build 16299.64) and Chrome (Version 63.0.3239.84)
Bug is no more reproducible on the target machine (one of maxxto...@). Issue may be closed.
Project Member

Comment 12 by sheriffbot@chromium.org, Dec 19 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: sandeepkumars@chromium.org
Status: WontFix (was: Unconfirmed)
Closing this issue as WontFix as per comment #11.

Thanks!!

Sign in to add a comment