We’ve been plagued for several years by occasional reports from customers about a non-descript error message «Cannot set allocations» that appears on startup of our app. We have never been able to reproduce the problem in our own test environments so far. I have now run out of ideas for attempting to track this down. Here’s a collection of observations that have accumulated over time:
- Error message text reads «Cannot set allocations» (note absence of punctuation).
- The window title simply reads «Error» (or the localized equivalent).
- The «Cannot set allocations» text is always in English regardless of OS locale.
-
I have so far not been able to locate the DLL or EXE containing the message text.
-
Google is chock full of reports of this error for a variety of different products — but no solutions.
-
The only unifying aspect between the affected products I could make out so far was that they all appear to come in the form of DLLs that load into third-party processes (such as addins for Visual Studio or Windows Explorer shell extensions).
-
Our app is actually a shareware COM-addin for MS Outlook, written in Delphi (i.e. native code — no .NET).
-
The prime suspect in our case is the third-party licensing wrapper that we’re using which decrypts and uncompresses our DLL into memory on the fly. Obviously I couldn’t simply give an unprotected version of our app to the affected customers to verify this suspicion. Maybe the other vendors that this has been reported against are using similar products.
-
Debug versions of the protection wrapper supplied to us by the licensing vendor yielded no results: The log files looked exactly the same as from sessions where the error did not occur. Apparently the «inner» DLL gets decrypted and uncompressed all right but for some reason still fails to get loaded by the host process.
-
By creating an unprotected «loader» DLL we have been able to pinpoint the occurrence of the error somewhere behind the
LoadLibrarycall that is supposed to load our DLL into memory. -
Extensive logging and global exception hooks in our own code (both the unprotected loader and the protected «core»-DLL) yielded no results at all. The error is obviously raised somewhere else.
-
The problem described in this earlier question of mine was very probably prompted by the same issue. This was before we created the unprotected loader stub.
-
The error only occurs at about 1-2% of our customers — whereas typically all installations at any affected customer’s site are affected the same.
- Sometimes the error goes away after we release a new version but often it will come back again after a couple of weeks or months.
- Once the error has started to occur on a machine it does so consistently.
-
The error never occurs while connected to the affected machine via remote access (e.g. VNC, RDP, TeamViewer, etc.) and none of the affected customers are within travel distance from us so all we have to go by is log files and «eye-witness reports».
-
One customer reported that the error message dialog apparently was non-modal, i.e. he was able to simply move the dialog box to the side and continue working with the application (minus the functionality that our DLL would have provided). Not sure whether this is universally true in all other occurrences, too.
-
In some cases customers have been able to permanently rid themselves of the error by disabling or uninstalling other addins from other vendors that were sharing the host application with our own product.
-
The error has so far been observed on Windows XP, Vista and 7.
-
During the last few weeks we had a surge of reports from Outlook 2003 / Windows 7 users. Could the situation have been made worse by a recent Windows/Office-update?
Does anyone have any experience with this error at all?
Or any more ideas for investigating this?
asked Apr 28, 2010 at 15:41
Oliver GiesenOliver Giesen
9,0996 gold badges46 silver badges82 bronze badges
I have only recently had this happen, which prompted my search and I ended up here. I can tell you that with me for sure it is in windows 7 home premium BUT ONLY WITH IE9 (which I hate by the way) it reduces the user back to the dummy stage and assumes that we have to be repeated flagged about everything.It will keep asking you if you want to disable add ons to speed up load times but usually on things that aren’t really the things slowing the browser down in the first place,it is there is too much garbage loading in the first place.But back to the «Cannot set allocations», I for one have never expirianced it in any other browser which is not to say it doesn’t happen with them.
answered Nov 29, 2012 at 7:52
This is going to be pure guess-work, but it sounds like maybe your third-party licensing software is trying to load your DLL at a particular location in memory, which — on these failing systems — happens to already be occupied by something else, perhaps a global hook DLL.
answered Apr 28, 2010 at 18:59
2
If you have a customer who is willing to work with you a bit, it might shed some light on the situation to get a crash dump (e.g., with ADPlus or maybe simpler with Sysinternals’ ProcDump) when the error message is showing. That would show what modules are loaded and possibly the callstack (if it is from a message box at the time of the error as opposed to one that is catching an exception after the problem).
answered Apr 28, 2010 at 17:59
Mark WilkinsMark Wilkins
40.7k5 gold badges57 silver badges110 bronze badges
2
I also have experienced the «Cannot set allocations» issue. Royal pain. I had disabled Java, since I did not seem to need it, I used add/remove programs to remove Java from my system. Then I stated to get those errors. I have reinstalled, but disabled Java in IE explorer. Now I do not get the error anymore. Not a programmer, don’t know why this happened. Maybe a clue for someone.
Win 7 — 64bit OS IE Explorer 10. Hope this helps someone figure this out. John
answered Mar 22, 2013 at 22:18
I’ve seen this happen. In my case a global hook dll created a large memory file mapping, perhaps to the memory the licensing dll was counting on.
answered Jun 6, 2014 at 13:56
vt.vt.
1,30712 silver badges27 bronze badges
I see «Cannot set Allocations» when I open google chrome only. Also after that, chrome closes with a msg saying «Whoa chrome has crashed…»
Still no solution 
answered May 31, 2015 at 21:32
YogurtuYogurtu
2,5763 gold badges23 silver badges22 bronze badges
1
Also not a programmer, but it always happens when I open Chrome. It opens second window with error message ‘cannot set allocation’. I usually close it and go on my way. if i don’t it usually causes a crash. doesnt happen on any other browsers.
answered Oct 26, 2015 at 13:17
0
Solution 1
This is going to be pure guess-work, but it sounds like maybe your third-party licensing software is trying to load your DLL at a particular location in memory, which — on these failing systems — happens to already be occupied by something else, perhaps a global hook DLL.
Solution 2
I have only recently had this happen, which prompted my search and I ended up here. I can tell you that with me for sure it is in windows 7 home premium BUT ONLY WITH IE9 (which I hate by the way) it reduces the user back to the dummy stage and assumes that we have to be repeated flagged about everything.It will keep asking you if you want to disable add ons to speed up load times but usually on things that aren’t really the things slowing the browser down in the first place,it is there is too much garbage loading in the first place.But back to the «Cannot set allocations», I for one have never expirianced it in any other browser which is not to say it doesn’t happen with them.
Solution 3
If you have a customer who is willing to work with you a bit, it might shed some light on the situation to get a crash dump (e.g., with ADPlus or maybe simpler with Sysinternals’ ProcDump) when the error message is showing. That would show what modules are loaded and possibly the callstack (if it is from a message box at the time of the error as opposed to one that is catching an exception after the problem).
Comments
-
We’ve been plagued for several years by occasional reports from customers about a non-descript error message «Cannot set allocations» that appears on startup of our app. We have never been able to reproduce the problem in our own test environments so far. I have now run out of ideas for attempting to track this down. Here’s a collection of observations that have accumulated over time:
- Error message text reads «Cannot set allocations» (note absence of punctuation).
- The window title simply reads «Error» (or the localized equivalent).
- The «Cannot set allocations» text is always in English regardless of OS locale.
-
I have so far not been able to locate the DLL or EXE containing the message text.
-
Google is chock full of reports of this error for a variety of different products — but no solutions.
-
The only unifying aspect between the affected products I could make out so far was that they all appear to come in the form of DLLs that load into third-party processes (such as addins for Visual Studio or Windows Explorer shell extensions).
-
Our app is actually a shareware COM-addin for MS Outlook, written in Delphi (i.e. native code — no .NET).
-
The prime suspect in our case is the third-party licensing wrapper that we’re using which decrypts and uncompresses our DLL into memory on the fly. Obviously I couldn’t simply give an unprotected version of our app to the affected customers to verify this suspicion. Maybe the other vendors that this has been reported against are using similar products.
-
Debug versions of the protection wrapper supplied to us by the licensing vendor yielded no results: The log files looked exactly the same as from sessions where the error did not occur. Apparently the «inner» DLL gets decrypted and uncompressed all right but for some reason still fails to get loaded by the host process.
-
By creating an unprotected «loader» DLL we have been able to pinpoint the occurrence of the error somewhere behind the
LoadLibrarycall that is supposed to load our DLL into memory. -
Extensive logging and global exception hooks in our own code (both the unprotected loader and the protected «core»-DLL) yielded no results at all. The error is obviously raised somewhere else.
-
The problem described in this earlier question of mine was very probably prompted by the same issue. This was before we created the unprotected loader stub.
-
The error only occurs at about 1-2% of our customers — whereas typically all installations at any affected customer’s site are affected the same.
- Sometimes the error goes away after we release a new version but often it will come back again after a couple of weeks or months.
- Once the error has started to occur on a machine it does so consistently.
-
The error never occurs while connected to the affected machine via remote access (e.g. VNC, RDP, TeamViewer, etc.) and none of the affected customers are within travel distance from us so all we have to go by is log files and «eye-witness reports».
-
One customer reported that the error message dialog apparently was non-modal, i.e. he was able to simply move the dialog box to the side and continue working with the application (minus the functionality that our DLL would have provided). Not sure whether this is universally true in all other occurrences, too.
-
In some cases customers have been able to permanently rid themselves of the error by disabling or uninstalling other addins from other vendors that were sharing the host application with our own product.
-
The error has so far been observed on Windows XP, Vista and 7.
-
During the last few weeks we had a surge of reports from Outlook 2003 / Windows 7 users. Could the situation have been made worse by a recent Windows/Office-update?
Does anyone have any experience with this error at all?
Or any more ideas for investigating this?
Recents
Related
-
windows
-
debugging
-
memory
-
dll
-
loadlibrary
- 02-10-2019
|
Question
We’ve been plagued for several years by occasional reports from customers about a non-descript error message «Cannot set allocations» that appears on startup of our app. We have never been able to reproduce the problem in our own test environments so far. I have now run out of ideas for attempting to track this down. Here’s a collection of observations that have accumulated over time:
- Error message text reads «Cannot set allocations» (note absence of punctuation).
- The window title simply reads «Error» (or the localized equivalent).
- The «Cannot set allocations» text is always in English regardless of OS locale.
-
I have so far not been able to locate the DLL or EXE containing the message text.
-
Google is chock full of reports of this error for a variety of different products — but no solutions.
-
The only unifying aspect between the affected products I could make out so far was that they all appear to come in the form of DLLs that load into third-party processes (such as addins for Visual Studio or Windows Explorer shell extensions).
-
Our app is actually a shareware COM-addin for MS Outlook, written in Delphi (i.e. native code — no .NET).
-
The prime suspect in our case is the third-party licensing wrapper that we’re using which decrypts and uncompresses our DLL into memory on the fly. Obviously I couldn’t simply give an unprotected version of our app to the affected customers to verify this suspicion. Maybe the other vendors that this has been reported against are using similar products.
-
Debug versions of the protection wrapper supplied to us by the licensing vendor yielded no results: The log files looked exactly the same as from sessions where the error did not occur. Apparently the «inner» DLL gets decrypted and uncompressed all right but for some reason still fails to get loaded by the host process.
-
By creating an unprotected «loader» DLL we have been able to pinpoint the occurrence of the error somewhere behind the
LoadLibrarycall that is supposed to load our DLL into memory. -
Extensive logging and global exception hooks in our own code (both the unprotected loader and the protected «core»-DLL) yielded no results at all. The error is obviously raised somewhere else.
-
The problem described in this earlier question of mine was very probably prompted by the same issue. This was before we created the unprotected loader stub.
-
The error only occurs at about 1-2% of our customers — whereas typically all installations at any affected customer’s site are affected the same.
- Sometimes the error goes away after we release a new version but often it will come back again after a couple of weeks or months.
- Once the error has started to occur on a machine it does so consistently.
-
The error never occurs while connected to the affected machine via remote access (e.g. VNC, RDP, TeamViewer, etc.) and none of the affected customers are within travel distance from us so all we have to go by is log files and «eye-witness reports».
-
One customer reported that the error message dialog apparently was non-modal, i.e. he was able to simply move the dialog box to the side and continue working with the application (minus the functionality that our DLL would have provided). Not sure whether this is universally true in all other occurrences, too.
-
In some cases customers have been able to permanently rid themselves of the error by disabling or uninstalling other addins from other vendors that were sharing the host application with our own product.
-
The error has so far been observed on Windows XP, Vista and 7.
-
During the last few weeks we had a surge of reports from Outlook 2003 / Windows 7 users. Could the situation have been made worse by a recent Windows/Office-update?
Does anyone have any experience with this error at all?
Or any more ideas for investigating this?
Solution
This is going to be pure guess-work, but it sounds like maybe your third-party licensing software is trying to load your DLL at a particular location in memory, which — on these failing systems — happens to already be occupied by something else, perhaps a global hook DLL.
OTHER TIPS
I have only recently had this happen, which prompted my search and I ended up here. I can tell you that with me for sure it is in windows 7 home premium BUT ONLY WITH IE9 (which I hate by the way) it reduces the user back to the dummy stage and assumes that we have to be repeated flagged about everything.It will keep asking you if you want to disable add ons to speed up load times but usually on things that aren’t really the things slowing the browser down in the first place,it is there is too much garbage loading in the first place.But back to the «Cannot set allocations», I for one have never expirianced it in any other browser which is not to say it doesn’t happen with them.
If you have a customer who is willing to work with you a bit, it might shed some light on the situation to get a crash dump (e.g., with ADPlus or maybe simpler with Sysinternals’ ProcDump) when the error message is showing. That would show what modules are loaded and possibly the callstack (if it is from a message box at the time of the error as opposed to one that is catching an exception after the problem).
I also have experienced the «Cannot set allocations» issue. Royal pain. I had disabled Java, since I did not seem to need it, I used add/remove programs to remove Java from my system. Then I stated to get those errors. I have reinstalled, but disabled Java in IE explorer. Now I do not get the error anymore. Not a programmer, don’t know why this happened. Maybe a clue for someone.
Win 7 — 64bit OS IE Explorer 10. Hope this helps someone figure this out. John
I’ve seen this happen. In my case a global hook dll created a large memory file mapping, perhaps to the memory the licensing dll was counting on.
I see «Cannot set Allocations» when I open google chrome only. Also after that, chrome closes with a msg saying «Whoa chrome has crashed…»
Still no solution
Also not a programmer, but it always happens when I open Chrome. It opens second window with error message ‘cannot set allocation’. I usually close it and go on my way. if i don’t it usually causes a crash. doesnt happen on any other browsers.
|
azhaurn Divine Member
Posts: 115Likes: 19 Currently Offline View Profile |
Post by azhaurn on Aug 21, 2020 10:40:59 GMTThis is a common error on Windows 10. I had this issue when buying a new PC and found right now how to fix it. Tutorial Repeat the same step on loader.exe and ElfCrack.exe. Try to crack now and check if it’s working now when you try to open the elfbot. If you still have the same issue, try the other options on the step 3*. You don’t need to restart the PC after making these changes. It worked for me. |
|
Last Edit: Aug 21, 2020 10:53:37 GMT by azhaurn |
Google Chrome crashes often on my system. Sometimes it says «Cannot set allocations» and other times it shows «The instruction at 0x0000000067CB1514 referenced memory at 0x00000000E9E44D9B. The memory could not be read.»
I noticed this usually happens when opening up to YouTube or Facebook. But it can happen other times too.
My computer specs:
Windows 10
32 gigs of ram
500gb SSD
Nvidia gtx880m
Only happens in chrome… Mozilla or IE work fine..
UPDATE:
So today I open Chrome and go to check on this question and I get yet another error:
I also tried running the Chrome Cleanup tool. No luck.
EDIT: I generated a dump here:
Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.
Show DivPrimary Analysis
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Version 10240 MP (8 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
kernel32.dll version: 10.0.10240.16384 (th1.150709-1700)
Machine Name:
Debug session time: Sun Oct 11 19:44:08.000 2015 (UTC - 4:00)
System Uptime: not available
Process Uptime: 0 days 0:02:06.000
Kernel time: 0 days 0:00:03.000
User time: 0 days 0:00:13.000
TRIAGER: Could not open triage file : e:dump_analysisprogramtriageoca.ini, error 2
TRIAGER: Could not open triage file : e:dump_analysisprogramwinxptriage.ini, error 2
TRIAGER: Could not open triage file : e:dump_analysisprogramtriageuser.ini, error 2
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
*** WARNING: Unable to verify timestamp for chrome.exe
*** ERROR: Module load completed but symbols could not be loaded for chrome.exe
TRIAGER: Could not open triage file : e:dump_analysisprogramtriageguids.ini, error 2
TRIAGER: Could not open triage file : e:dump_analysisprogramtriagemodclass.ini, error 2
*** The OS name list needs to be updated! Unknown Windows version: 10.0 ***
FAULTING_IP:
chrome_6e130000+3bf8f2
6e4ef8f2 ff34b8 push dword ptr [eax+edi*4]
EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 6e4ef8f2 (chrome_6e130000+0x003bf8f2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 8deee641
Attempt to read from address 8deee641
DEFAULT_BUCKET_ID: INVALID_POINTER_READ
PROCESS_NAME: chrome.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 8deee641
READ_ADDRESS: 8deee641
FOLLOWUP_IP:
chrome_6e130000+3bf8f2
6e4ef8f2 ff34b8 push dword ptr [eax+edi*4]
NTGLOBALFLAG: 0
FAULTING_THREAD: 0000032c
PRIMARY_PROBLEM_CLASS: INVALID_POINTER_READ
BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ
LAST_CONTROL_TRANSFER: from 6e4ef74b to 6e4ef8f2
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
001aef28 6e4ef74b 00000056 00000000 0756df28 chrome_6e130000+0x3bf8f2
001aef68 6e4ef46e 0756df28 6fa3447c 001af058 chrome_6e130000+0x3bf74b
001aef80 6e4edf97 0756df28 07961ea0 0756df28 chrome_6e130000+0x3bf46e
001af058 6e3b2bd2 6feed4c0 0c31ef58 00000004 chrome_6e130000+0x3bdf97
001af380 6e4e5259 0c31ef58 0c31ef58 07675958 chrome_6e130000+0x282bd2
001af3b8 6e4dab6f 6e4da733 0c31ef58 07675958 chrome_6e130000+0x3b5259
001af3d4 6e4da9a2 128ce550 6e4da733 06c18798 chrome_6e130000+0x3aab6f
001af434 6e4da65a 128ce550 001af590 00000000 chrome_6e130000+0x3aa9a2
001af454 6e177e51 128ce530 001af590 02682f00 chrome_6e130000+0x3aa65a
001af53c 6e177b23 00000000 00000038 001af590 chrome_6e130000+0x47e51
001af574 6e177567 001af590 02662fc8 02662fc0 chrome_6e130000+0x47b23
001af6a8 6e231eb7 00000000 02662fc0 00000000 chrome_6e130000+0x47567
001af6c4 6e177043 00216230 02682f00 02682f00 chrome_6e130000+0x101eb7
001af6e4 6e176f4c 02682f00 00216230 001af744 chrome_6e130000+0x47043
001af708 6e176e54 6feed4ad 6feed4ad 015f7638 chrome_6e130000+0x46f4c
001af730 6e43fa4f 6f92af25 00216118 6fa644a8 chrome_6e130000+0x46e54
001af778 6e43f98e 00216128 ffffffff 02669410 chrome_6e130000+0x30fa4f
001af79c 6e150733 0029b030 00000000 002a1450 chrome_6e130000+0x30f98e
001af7cc 6e150571 001af7fc 002cb720 00000000 chrome_6e130000+0x20733
001af7e0 6e1504ed 001af810 001af7fc 001af854 chrome_6e130000+0x20571
001af82c 6e137671 00000000 002f3b60 001af87c chrome_6e130000+0x204ed
001af83c 6e136832 001af86c 00c87bea 00cc52b0 chrome_6e130000+0x7671
001af87c 00c6958c 00c40000 001af898 00c8cee4 chrome_6e130000+0x6832
001af95c 00c68a7c 00c40000 00000001 00000000 chrome+0x2958c
001afa54 00c8ce6a 00c40000 00000000 00211f06 chrome+0x28a7c
001afaa0 75923744 fe35e000 75923720 6f1cd5d9 chrome+0x4ce6a
001afab4 7753a064 fe35e000 ecf34ab8 00000000 kernel32!BaseThreadInitThunk+0x24
001afafc 7753a02f ffffffff 7755d7b0 00000000 ntdll!__RtlUserThreadStart+0x2f
001afb0c 00000000 00c8cee4 fe35e000 00000000 ntdll!_RtlUserThreadStart+0x1b
STACK_COMMAND: ~0s; .ecxr ; kb
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: chrome_6e130000+3bf8f2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: chrome_6e130000
IMAGE_NAME: chrome.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 56033dd8
FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_chrome.dll!Unknown
BUCKET_ID: APPLICATION_FAULT_INVALID_POINTER_READ_chrome_6e130000+3bf8f2
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/chrome_exe/45_0_2454_101/56034380/chrome_dll/45_0_2454_101/56033dd8/c0000005/003bf8f2.htm?Retriage=1
Followup: MachineOwner
---------
This free analysis is provided by OSR Open Systems Resources, Inc.
Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)
Show DivLoaded Module List
Show DivRaw Stack Contents
Show DivDump Header Information
Show DivStrings
More details on stackdump
=================================================
Stack Trace: For the Crash ID - b56d2a222d37b962
=================================================
Thread 0 CRASHED [EXCEPTION_ACCESS_VIOLATION_READ @ 0xffffffff8deee800 ] MAGIC SIGNATURE THREAD
0x6e4ef8f2 (chrome.dll -rolling_time_delta_history.cc:21 ) cc::RollingTimeDeltaHistory::InsertSample(base::TimeDelta)
0x6e4ef74a (chrome.dll -compositor_timing_history.cc:112 ) cc::CompositorTimingHistory::DidCommit()
0x6e4ef46d (chrome.dll -single_thread_proxy.cc:294 ) cc::SingleThreadProxy::CommitComplete()
0x6e4edf96 (chrome.dll -layer_tree_host_impl.cc:1958 ) cc::LayerTreeHostImpl::ActivateSyncTree()
0x6e3b2bd1 (chrome.dll -scheduler.cc:659 ) cc::Scheduler::ProcessScheduledActions()
0x6e4e5258 (chrome.dll -scheduler.cc:219 ) cc::Scheduler::NotifyReadyToCommit()
0x6e4dab6e (chrome.dll -single_thread_proxy.cc:853 ) cc::SingleThreadProxy::DoBeginMainFrame(cc::BeginFrameArgs const &)
0x6e4da9a1 (chrome.dll -single_thread_proxy.cc:833 ) cc::SingleThreadProxy::BeginMainFrame(cc::BeginFrameArgs const &)
0x6e4da659 (chrome.dll -bind_internal.h:346 ) base::internal::Invoker<base::IndexSequence<0,1>,base::internal::BindState<base::internal::RunnableAdapter<void ( cc::SingleThreadProxy::*)(cc::BeginFrameArgs const &)>,void ,base::internal::TypeList<base::WeakPtr<cc::SingleThreadProxy>,cc::BeginFrameArgs>
,base::internal::TypeList<base::internal::UnwrapTraits<base::WeakPtr<cc::SingleThreadProxy> ,base::internal::UnwrapTraits<cc::BeginFrameArgs> ,base::internal::InvokeHelper<1,void,base::internal::RunnableAdapter<void
( cc::SingleThreadProxy::*)(cc::BeginFrameArgs const &)>,base::internal::TypeList<base::WeakPtr<cc::SingleThreadProxy> const &,cc::BeginFrameArgs const &> >,void >::Run(base::internal::BindStateBase *)
0x6e177e50 (chrome.dll -task_annotator.cc:62 ) base::debug::TaskAnnotator::RunTask(char const *,char const *,base::PendingTask const &)
0x6e177b22 (chrome.dll -message_loop.cc:473 ) base::MessageLoop::RunTask(base::PendingTask const &)
0x6e177566 (chrome.dll -message_loop.cc:594 ) base::MessageLoop::DoWork()
0x6e231eb6 (chrome.dll -message_pump_win.cc:184 ) base::MessagePumpForUI::DoRunLoop()
0x6e177042 (chrome.dll -message_pump_win.cc:57 ) base::MessagePumpWin::Run(base::MessagePump::Delegate *)
0x6e176f4b (chrome.dll -message_loop.cc:438 ) base::MessageLoop::RunHandler()
0x6e176e53 (chrome.dll -run_loop.cc:55 ) base::RunLoop::Run()
0x6e43fa4e (chrome.dll -chrome_browser_main.cc:1709 ) ChromeBrowserMainParts::MainMessageLoopRun(int *)
0x6e43f98d (chrome.dll -browser_main_loop.cc:877 ) content::BrowserMainLoop::RunMainMessageLoopParts()
0x6e43f952 (chrome.dll -browser_main_runner.cc:211 ) content::BrowserMainRunnerImpl::Run()
0x6e150732 (chrome.dll -browser_main.cc:26 ) content::BrowserMain(content::MainFunctionParams const &)
0x6e150570 (chrome.dll -content_main_runner.cc:384 ) content::RunNamedProcessTypeMain(std::basic_string<char,std::char_traits<char>,std::allocator<char>
const &,content::MainFunctionParams const &,content::ContentMainDelegate
*)
0x6e1504ec (chrome.dll -content_main_runner.cc:808 ) content::ContentMainRunnerImpl::Run()
0x6e137670 (chrome.dll -content_main.cc:19 ) content::ContentMain(content::ContentMainParams const &)
0x6e136831 (chrome.dll -chrome_main.cc:66 ) ChromeMain
0x00c6958b (chrome.exe -client_util.cc:252 ) MainDllLoader::Launch(HINSTANCE__ *)
0x00c68a7b (chrome.exe -chrome_exe_main_win.cc:157 ) wWinMain
0x00c8ce69 (chrome.exe -crt0.c:251 ) __tmainCRTStartup
0x75923743 (kernel32.dll + 0x00013743 ) BaseThreadInitThunk
0x7753a063 (ntdll.dll + 0x0005a063 ) __RtlUserThreadStart
0x7753a02e (ntdll.dll + 0x0005a02e ) _RtlUserThreadStart
EDIT:
Link to .zip with dump file:
https://drive.google.com/file/d/0B8IQnsZbQdI_LV9ROWo2YTByVDQ/view?usp=sharing