Closed
Bug 935107
Opened 12 years ago
Closed 12 years ago
NIghtly Build ID 20131105030206 startup crash with ntdll.dll signature
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 935280
People
(Reporter: semtex2, Unassigned)
Details
(Keywords: crash)
Attachments
(1 file)
|
83.35 KB,
text/x-log
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0 (Beta/Release)
Build ID: 20131105030206
Steps to reproduce:
Nightly update to: https://hg.mozilla.org/mozilla-central/rev/770de5942471
Actual results:
Browser did restart and crash on startup with: https://crash-stats.mozilla.com/report/index/c8d3f690-e42c-4556-b06c-ef77f2131105
Not possible to run in save mode (same crash), I've installed previous build, reset profile, same problem in save and normal mode.
I need to uninstall completely Nightly from system, install again and recover profile from backup, no problems after this, Nightly starts normal.
More reports from today: https://crash-stats.mozilla.com/report/list?signature=ntdll.dll%400x39132&product=Firefox&query_type=contains&range_unit=weeks&process_type=any&hang_type=any&date=2013-11-05+18%3A00%3A00&range_value=1#reports
Comment 1•12 years ago
|
||
FAULTING_SOURCE_CODE:
No source found for 'e:\builds\moz2_slave\m-cen-w64-ntly-000000000000000\build\xpcom\ds\nswindowsregkey.cpp'
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: xul!nsWindowsRegKey::ReadStringValue+130
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: xul
IMAGE_NAME: xul.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 5278ddb4
STACK_COMMAND: ~0s ; kb
FAILURE_BUCKET_ID: INVALID_POINTER_WRITE_c0000005_xul.dll!nsWindowsRegKey::ReadStringValue
BUCKET_ID: X64_APPLICATION_FAULT_INVALID_POINTER_WRITE_xul!nsWindowsRegKey::ReadStringValue+130
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/firefox_exe/28_0_0_5057/5278ddf5/ntdll_dll/6_3_9600_16408/523d5305/c0000005/0009a2ea.htm?Retriage=1
Followup: MachineOwner
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•