1411998 - thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', src/libcore/option.rs:335:20

Status: UNCONFIRMED

(Core :: General, defect)

Description

[Wellington Torrejais da Silva]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0
Build ID: 20171024130124

Steps to reproduce:

Just try to close bowser with opened tabs(some tabs) by CTRL+Q (Keyboard Shortcut)

And got too but I do not know  this is related?
Corrupt JPEG data: bad Huffman code







Actual results:

Big Error when try to close browser:

thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', src/libcore/option.rs:335:20
stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>
  16: <unknown>
  17: <unknown>
  18: <unknown>
  19: <unknown>
  20: <unknown>
  21: <unknown>
  22: <unknown>
  23: <unknown>
  24: <unknown>
  25: <unknown>
  26: <unknown>
  27: <unknown>
  28: <unknown>
  29: <unknown>
  30: <unknown>
  31: <unknown>
  32: <unknown>
  33: <unknown>
  34: <unknown>
  35: <unknown>
  36: <unknown>
  37: <unknown>
  38: <unknown>
  39: <unknown>
  40: <unknown>
  41: <unknown>
  42: <unknown>
  43: <unknown>
  44: <unknown>
  45: <unknown>
  46: <unknown>
  47: <unknown>
  48: <unknown>
  49: <unknown>
  50: <unknown>
  51: __libc_start_main
  52: _start
Redirecting call to abort() to mozalloc_abort



Expected results:

No errors, fine closing and fine destroy sequence.

Thanks...

Comment 1

[Marius Coman [:mcoman], Ecosystem QA]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0
Firefox: 58.0a1, Build ID 20171030103605

I have not managed to reproduce the issue on Ubuntu 14.04 x64, Arch Linux x64 and Windows 10 x64 using the latest Nightly build (58.0a1).
Are you using an official Mozilla binary? If no, could you please download Nightly from https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly and try to reproduce the issue?
Also, if possible, could you please list some of the websites that are opened when the "destroy sequence" command is applied?

Comment 2

[Wellington Torrejais da Silva]

(In reply to Marius Coman [:cmarius] from comment #1)
> User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101
> Firefox/58.0
> Firefox: 58.0a1, Build ID 20171030103605
> 
> I have not managed to reproduce the issue on Ubuntu 14.04 x64, Arch Linux
> x64 and Windows 10 x64 using the latest Nightly build (58.0a1).
> Are you using an official Mozilla binary? If no, could you please download
> Nightly from https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly
> and try to reproduce the issue?
> Also, if possible, could you please list some of the websites that are
> opened when the "destroy sequence" command is applied?

It's not from specific site. Yes it is official binary. 
I'm observed certain relation between error and high processor usage/parallelism.

I'm will wait for more errors and in the next crash with this messages I will reply this comment.
Can you try or simulate if that problem occurs with you at limited resources environment?

Thanks.

Comment 3

[Marius Coman [:mcoman], Ecosystem QA]

Attachment: console output.txt

I've have not managed to reproduce this issue on Ubuntu 14.04 x64 using the latest Nightly (build ID 20171102100041), under a limited resources environment.

I've opened Google Chrome, loaded 61 Youtube tabs and I've copied a file from a USB stick to the hard disk. The CPU was at 98% and the memory usage was at 6.1 GB from a total of 8gb.
After I've pressed "Ctrl+Q", no errors appeared in my console related to:

 "thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', src/libcore/option.rs:335:20
stack backtrace:
   0: <unknown>
   1: <unknown>"
  
In the attachment you will find the console output that was displayed after the "destroy sequence" command was applied.

Comment 4

[Wellington Torrejais da Silva]

Hi,

I still have the problems. Is there a way I can help?

Thanks.

Comment 5

[Marius Coman [:mcoman], Ecosystem QA]

(In reply to Wellington Torrejais da Silva from comment #4)
> I still have the problems. Is there a way I can help?
@Panos, do you have any sugestions regarding this?

Comment 6

[Panos Astithas (he/him) [:past] (please ni?)]

I'm not familiar with the rust integration bits and I don't know why we don't see stack frame information in comment 0. Ralph might know.

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit auto_nag documentation.