startup crash [@ SHA256_Compress ]
Categories
(NSS :: Libraries, defect, P5)
Tracking
(firefox47 affected, firefox48 affected, firefox49 affected, firefox-esr45 affected, firefox51 affected)
People
(Reporter: Usul, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: crash, Whiteboard: [gs][tbird crash][rare][startupcrash][nss-monitor])
Crash Data
Updated•14 years ago
|
Comment 1•14 years ago
|
||
Comment 2•12 years ago
|
||
Comment 3•9 years ago
|
||
Comment 4•9 years ago
|
||
Comment 5•7 years ago
|
||
Is this even a crypto crash?
Only one version 60 crash in 6 months bp-8a9245dc-e1c7-4308-b4eb-631960181226
Comment 6•7 years ago
|
||
Various reasons for crashing, most seem illegal instructions, like the instruction pointer pointing a location that doesn't contain valid assembler code, or assembler code not permissible outside the kernel level. Discussions on stackoverflow suggest that a corrupted stack or invalid function pointers is likely. The crash on TB 60 branch in NSS sha512.c happens while moving data around within a block of memory, to calculate a hash. This should trigger an invalid code exception, except when the memory it's working on is already bad.
Comment 7•7 years ago
|
||
s/should trigger/shouldn't trigger/
Comment 8•3 years ago
|
||
Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 9•1 year ago
|
||
Closing because no crashes reported for 12 weeks.
Description
•