Old 03-19-2021, 05:32 AM   #1
Gass n Klang
Human being with feelings
 
Gass n Klang's Avatar
 
Join Date: Nov 2015
Location: Cologne
Posts: 1,636
Default Initializing...

Opening the first project after starting reaper is never a problem. opening the second project reaper often hangs in "Initializing...". Not a good thing if you want to copy from one project to another ...
Strange is that I can scroll and zoom on the "half-loaded" project already. But the Initializing Screen won't dissappear.


If I open a new project tab first and then load the project I want, it seems to work.


EDIT: wow! it depends on the mixer visible on a second screen. Having the mixer docked does not lead to any problems as it seems.
__________________
https://juliusgass.de

Last edited by Gass n Klang; 08-13-2021 at 12:01 AM.
Gass n Klang is online now   Reply With Quote
Old 06-16-2021, 03:07 AM   #2
Gass n Klang
Human being with feelings
 
Gass n Klang's Avatar
 
Join Date: Nov 2015
Location: Cologne
Posts: 1,636
Default

bump.
__________________
https://juliusgass.de
Gass n Klang is online now   Reply With Quote
Old 06-16-2021, 07:30 AM   #3
ramses
Human being with feelings
 
Join Date: Jul 2009
Posts: 1,231
Default

I believe this issue is related to certain plugins. If you try to identify what plugin is causing the issue, perhaps this could move the issue forward.
ramses is offline   Reply With Quote
Old 06-16-2021, 09:50 AM   #4
Meo-Ada Mespotine
Human being with feelings
 
Meo-Ada Mespotine's Avatar
 
Join Date: May 2017
Location: Leipzig
Posts: 6,621
Default

Try opening the second project with the "Open with FX offline(recovery mode)-checkbox set in the Open project-dialog.

If that works, it's probably a problematic plugin.
__________________
Use you/she/her.Ultraschall-Api Lua Api4Reaper - Donate, if you wish

On vacation for the time being...
Meo-Ada Mespotine is offline   Reply With Quote
Old 06-16-2021, 11:33 AM   #5
Gass n Klang
Human being with feelings
 
Gass n Klang's Avatar
 
Join Date: Nov 2015
Location: Cologne
Posts: 1,636
Default

mhh. I got the workaround with opening a new project tab first. Yes, probably it's a plugin and I can try to find out which one, but I wonder why the same plugins work in other DAWs without any problem. I use multiple DAWs in different studios and never have problems with the plugins I have.
__________________
https://juliusgass.de
Gass n Klang is online now   Reply With Quote
Old 06-17-2021, 07:00 AM   #6
ramses
Human being with feelings
 
Join Date: Jul 2009
Posts: 1,231
Default

Quote:
Originally Posted by Gass n Klang View Post
mhh. I got the workaround with opening a new project tab first. Yes, probably it's a plugin and I can try to find out which one, but I wonder why the same plugins work in other DAWs without any problem. I use multiple DAWs in different studios and never have problems with the plugins I have.
It could be many things. It could be a bug. Or it could be that other developers don't strictly follow the vst plugin protocols. Or it could be that Reaper don't strictly follow the vst plugin protocols. Or it could be other things. Until we know what plugin is causing the issue, it's impossible to say really.
ramses is offline   Reply With Quote
Old 08-10-2021, 06:21 AM   #7
Gass n Klang
Human being with feelings
 
Gass n Klang's Avatar
 
Join Date: Nov 2015
Location: Cologne
Posts: 1,636
Default

ok, everytime I create a new project, this happens. Even without plugins but as soon as I have a lot of media items in my project.
No problems with clean projects and never problems loading a new project tab instead of a new project.

I have all my projects on a USB-C external drive (Samsung T7), cause I often have to work on the road. This already was a problem sometimes when I wanted to backup my projects using "save as - copy all media into project directory, using..."

Would be super cool if that could be fixed somehow.
__________________
https://juliusgass.de
Gass n Klang is online now   Reply With Quote
Old 08-10-2021, 10:38 AM   #8
ramses
Human being with feelings
 
Join Date: Jul 2009
Posts: 1,231
Default

Does it happen when you go from an audio-heavy project to an empty project as well? Vice versa?

Try this. Does it matter if you have the mixer visible or not? There are issues with having the mixer open in its own window on a second screen for some reason.
ramses is offline   Reply With Quote
Old 08-10-2021, 02:38 PM   #9
Gass n Klang
Human being with feelings
 
Gass n Klang's Avatar
 
Join Date: Nov 2015
Location: Cologne
Posts: 1,636
Default It's the mixer window!

Quote:
Originally Posted by ramses View Post
Does it happen when you go from an audio-heavy project to an empty project as well? Vice versa?

Try this. Does it matter if you have the mixer visible or not? There are issues with having the mixer open in its own window on a second screen for some reason.
wow! it depends on the mixer visible on a second screen. Having the mixer docked does not lead to any problems as it seems. weird!
__________________
https://juliusgass.de

Last edited by Gass n Klang; 08-10-2021 at 04:22 PM.
Gass n Klang is online now   Reply With Quote
Old 08-10-2021, 02:56 PM   #10
alanofoz
Human being with feelings
 
alanofoz's Avatar
 
Join Date: Sep 2009
Location: Oz - Blue Mountains NSW, formerly Geelong
Posts: 943
Default

Quote:
Originally Posted by Gass n Klang View Post
wow! it depends on the mixer visible on a second screen. Having the mixer docked does not lead to any problems as it seems. weird!
I have the mixer in a separate docker on a second screen with no problems. Haven't tried it floating on its own.
__________________
It's "its" except when it's "it is".

alanofoz, aka Alan of Australia
alanofoz is offline   Reply With Quote
Old 08-11-2021, 01:55 AM   #11
ramses
Human being with feelings
 
Join Date: Jul 2009
Posts: 1,231
Default

Quote:
Originally Posted by Gass n Klang View Post
wow! it depends on the mixer visible on a second screen. Having the mixer docked does not lead to any problems as it seems. weird!
Nice, so we're about to nail this issue down perhaps. Let me see, there's another thread for this issue.

https://forum.cockos.com/showthread....62#post2471062
ramses is offline   Reply With Quote
Old 08-11-2021, 05:58 AM   #12
ajawamnet
Human being with feelings
 
Join Date: Jun 2017
Posts: 172
Default

Yea - there's something weird going with graphics interaction with versions 6.3 on... I have the opposite problem where certain projects will not close and it hangs at "Initializing" - even with no plug ins loaded. When it does this the CPU goes up considerably.

Thing that's strange is that if I zoom the TCP all the way out, the CPU utilization drops and the same project will now close without hanging at "Initializing"

6.23 does no behave this way regardless of the zoom level of the TCP

Post here: https://forums.cockos.com/showthread.php?t=256285

Using Systernals Procmon, tracing the reaper.exe shows this.

At the end of the one that does NOT close you can see that Reaper never gets past IRP_MJ_CLOSE on the Reaper.ini.

58:34.1 reaper.exe 10780 IRP_MJ_CLEANUP
58:34.1 reaper.exe 10780 IRP_MJ_CLOSE
58:35.0 reaper.exe 10780 Process Profiling
58:36.0 reaper.exe 10780 Process Profiling
58:37.0 reaper.exe 10780 Process Profiling
58:38.0 reaper.exe 10780 Process Profiling - and on and on. Never completes...


The one that DOES close - which is the same file, just with the TCP zoomed out and scrolled to the bottom of the project, goes all the way through to:

02:31.8 reaper.exe 9860 IRP_MJ_CLEANUP
02:31.8 reaper.exe 9860 IRP_MJ_CLOSE
02:31.8 reaper.exe 9860 RegQueryKey
02:31.8 reaper.exe 9860 RegOpenKey
02:31.8 reaper.exe 9860 RegQueryValue
02:31.8 reaper.exe 9860 RegQueryValue
02:31.8 reaper.exe 9860 RegCloseKey
02:31.8 reaper.exe 9860 Thread Exit
02:31.8 reaper.exe 9860 RegQueryKey
02:31.8 reaper.exe 9860 RegOpenKey
02:31.8 reaper.exe 9860 RegQueryValue
02:31.8 reaper.exe 9860 RegQueryValue
02:31.8 reaper.exe 9860 RegCloseKey
02:32.1 reaper.exe 9860 Process Profiling
02:33.1 reaper.exe 9860 Process Profiling
02:34.1 reaper.exe 9860 Process Profiling
02:35.1 reaper.exe 9860 Process Profiling
02:36.1 reaper.exe 9860 Process Profiling
02:37.1 reaper.exe 9860 Process Profiling
02:38.1 reaper.exe 9860 Process Profiling
02:38.2 reaper.exe 9860 Thread Exit
02:38.2 reaper.exe 9860 Thread Exit
02:38.2 reaper.exe 9860 Thread Exit
02:38.2 reaper.exe 9860 Thread Exit
02:38.2 reaper.exe 9860 Thread Exit
02:38.2 reaper.exe 9860 Thread Exit
02:38.2 reaper.exe 9860 Thread Exit
02:38.2 reaper.exe 9860 Thread Exit
02:38.3 reaper.exe 9860 Thread Exit
02:38.3 reaper.exe 9860 Thread Exit
02:38.3 reaper.exe 9860 Thread Exit
02:38.3 reaper.exe 9860 Thread Exit
02:38.3 reaper.exe 9860 Thread Exit
02:38.3 reaper.exe 9860 Thread Exit
02:38.3 reaper.exe 9860 Thread Exit
02:38.5 reaper.exe 9860 Thread Exit
02:38.5 reaper.exe 9860 Thread Exit
02:39.1 reaper.exe 9860 Process Profiling

and exits.

Something weird going on here.
ajawamnet is offline   Reply With Quote
Old 08-12-2021, 05:00 PM   #13
ajawamnet
Human being with feelings
 
Join Date: Jun 2017
Posts: 172
Default

Quote:
Originally Posted by Gass n Klang View Post
Opening the first project after starting reaper is never a problem. opening the second project reaper often hangs in "Initializing...". Not a good thing if you want to copy from one project to another ...
Strange is that I can scroll and zoom on the "half-loaded" project already. But the Initializing Screen won't dissappear.


If I open a new project tab first and then load the project I want, it seems to work.

Same with the project close bug. It will hang on the initialize screen but I can still scroll through the TCP even though it's greyed out.
ajawamnet is offline   Reply With Quote
Old 08-12-2021, 05:13 PM   #14
karbomusic
Human being with feelings
 
karbomusic's Avatar
 
Join Date: May 2009
Posts: 29,260
Default

Apologies since I haven't read all the threads/posts closely and this has already been tested for the close bug but do you...

1. Have a project open, then click File > Open Project. Then you do File > Open Project again - In other words, any sequence where you have a project already open and it gets auto-closed by Reaper because you "open" another project to replace it.

Or do you...

2. Have a project open, then click File > Close Project. Then File > Open Project - Or any sequence where you fully close the first project THEN open the next project as a second step where the first project has already been completely closed.


If you have not tried #2, report back as to whether the issue reproduces that way.
__________________
Music is what feelings sound like.

Last edited by karbomusic; 08-12-2021 at 06:17 PM.
karbomusic is offline   Reply With Quote
Old 08-12-2021, 06:09 PM   #15
Jae.Thomas
Human being with feelings
 
Join Date: Jun 2006
Posts: 22,567
Default

some plugins don't like being closed
Jae.Thomas is offline   Reply With Quote
Old 08-12-2021, 06:19 PM   #16
karbomusic
Human being with feelings
 
karbomusic's Avatar
 
Join Date: May 2009
Posts: 29,260
Default

Quote:
Originally Posted by Jae.Thomas View Post
some plugins don't like being closed
When it's a plugin and also my scenario #1 above, "Allow complete unload of VST plug-ins" sometimes fixes it. There is a remote chance there is some scenario where reaper is waiting for it to unload fully but it doesn't, causing the initializing step of the opening project to hang.
__________________
Music is what feelings sound like.
karbomusic is offline   Reply With Quote
Old 08-12-2021, 07:23 PM   #17
karbomusic
Human being with feelings
 
karbomusic's Avatar
 
Join Date: May 2009
Posts: 29,260
Default

Some info of interest...

Quote:
Originally Posted by ajawamnet View Post
Using Systernals Procmon, tracing the reaper.exe shows this.

At the end of the one that does NOT close you can see that Reaper never gets past IRP_MJ_CLOSE on the Reaper.ini.

58:34.1 reaper.exe 10780 IRP_MJ_CLEANUP
58:34.1 reaper.exe 10780 IRP_MJ_CLOSE
58:35.0 reaper.exe 10780 Process Profiling
58:36.0 reaper.exe 10780 Process Profiling
58:37.0 reaper.exe 10780 Process Profiling
58:38.0 reaper.exe 10780 Process Profiling - and on and on. Never completes...
I think IRP_MJ_CLOSE is the function you care about there. "Process Profiling" is just Procmon profiling the process to get it's processing time. You'll get less noise if you disable that (icon looks like a green oscilloscope) in the display filter on the toolbar.

https://docs.microsoft.com/en-us/win...l/irp-mj-close

You can also double-click that entry and look at the "Stack" tab but if you don't have any symbols mapped it may lie to you. You can partially fix that by going to options > configure symbols like below:



I do not remember if the correct version of dbghelp.dll exist as in the picture above without installing the Windows Debugger which I think is where that dll comes from as it needs to be a particular version. Either way, when configured correctly, both Process Monitor and Process Explorer can give more accurate information when they can at least download Microsoft symbols which these settings are for.

Assuming that's working, the Stack view for IRP_MJ_CLOSE may call out who/what is leading up to it being called. Or not, since we don't have reapers code, it just depends on who's doing the calling (see side note below). I'm spewing all this at you since you seem to have good attention to detail and might want to know if you don't already.

=================
Side Note
=================

I just had this occur but it was for a completely different reason. Procmon logged zero IRP_MJ_*** calls from Reaper. But it was hung in initializing forever. I noticed that Arial font was being queried/mapped in an endless loop, for the entire 5 minutes I waited - hence the hang.



I started clicking on each of those entries then the stack tab and I noticed that VOLA2.dll (a vocal leveler VST) was the one at least kicking this off - it was in every event of this endless loop:



Hmm... I looked over at the hung reaper and noticed several FX windows were open and VOLA2 was one of them. I closed each FX window one at a time (as they where not hung). Then, I close Vola2 and bam, the project completes the close and the new project opens up.

So in my case, in my particular scenario, VOLA2 is up to something related to drawing text or cleaning up from it and it's looping. Reaper could still be involved in all scenarios, but it's good to know the above, and that the conditions that can cause a hung initializing screen can be more than a single set of conditions and/or root causes at least from the end-user view.
__________________
Music is what feelings sound like.

Last edited by karbomusic; 08-12-2021 at 07:36 PM.
karbomusic is offline   Reply With Quote
Old 08-13-2021, 08:31 AM   #18
ajawamnet
Human being with feelings
 
Join Date: Jun 2017
Posts: 172
Default

Quote:
Originally Posted by karbomusic View Post

So in my case, in my particular scenario, VOLA2 is up to something related to drawing text or cleaning up from it and it's looping. Reaper could still be involved in all scenarios, but it's good to know the above, and that the conditions that can cause a hung initializing screen can be more than a single set of conditions and/or root causes at least from the end-user view.
In my case with the file here https://forums.cockos.com/showpost.p...78&postcount=6 called wontclose_nofx.RPP has no plugins at all. And I even tried deleting all the monitor plugins in that session. Still hangs. And what's weird is like the other "initializing gets stuck" issues, it seems dependent on what or how stuff is displayed.
ajawamnet is offline   Reply With Quote
Old 08-13-2021, 08:36 AM   #19
karbomusic
Human being with feelings
 
karbomusic's Avatar
 
Join Date: May 2009
Posts: 29,260
Default

Quote:
Originally Posted by ajawamnet View Post
In my case with the file here https://forums.cockos.com/showpost.p...78&postcount=6 called wontclose_nofx.RPP has no plugins at all. And I even tried deleting all the monitor plugins in that session. Still hangs.
Yes, I'm aware of ^that already:

https://forum.cockos.com/showpost.ph...52&postcount=8

...and that project will not reproduce the issue here in 6.32. I noted that in that thread when testing earlier.

I still need to know if the issue reproduces in scenario #2 above in my other post - especially since I noticed you are using scenario #1 to close/open projects.

Secondly, you might also get those symbols correct for procmon and process explorer because you can see the stack which is the more accurate way to see what is waiting on what (just like my issue I solved above did).

It may work without symbols but regardles the wait chain/stack is more important than say CPU usage etc. Instructions for the stack view in procmon are in my other post, to see this in process explorer, double-click > threads > then each thread can be double clicked to see the stack. Bascially, find the thread ID in procmon that appears to have stalled, then go find that thread in process explorer.

In your issue, there is a wait to close/cleanup an object handle by/for a driver as I explained earlier.
__________________
Music is what feelings sound like.

Last edited by karbomusic; 08-13-2021 at 08:46 AM.
karbomusic is offline   Reply With Quote
Old 08-13-2021, 08:43 AM   #20
ajawamnet
Human being with feelings
 
Join Date: Jun 2017
Posts: 172
Default

When that wontclose_nofx.RPP hangs when I have 32 bit monitor FX loaded the IRP_MJ_CLOSE the stack for it in Procmon is:

0 FLTMGR.SYS FltDecodeParameters + 0x1cfc 0xfffff804334c4a5c C:\WINDOWS\System32\drivers\FLTMGR.SYS
1 FLTMGR.SYS FltDecodeParameters + 0x1840 0xfffff804334c45a0 C:\WINDOWS\System32\drivers\FLTMGR.SYS
2 FLTMGR.SYS FltDecodeParameters + 0x13b2 0xfffff804334c4112 C:\WINDOWS\System32\drivers\FLTMGR.SYS
3 FLTMGR.SYS FltDecodeParameters + 0x119e 0xfffff804334c3efe C:\WINDOWS\System32\drivers\FLTMGR.SYS
4 ntoskrnl.exe IofCallDriver + 0x59 0xfffff80431827da9 C:\WINDOWS\system32\ntoskrnl.exe
5 ntoskrnl.exe ProbeForWrite + 0x19d 0xfffff80431e13e4d C:\WINDOWS\system32\ntoskrnl.exe
6 ntoskrnl.exe SeQueryInformationToken + 0xff0 0xfffff80431e22470 C:\WINDOWS\system32\ntoskrnl.exe
7 ntoskrnl.exe ObfDereferenceObjectWithTag + 0xc9 0xfffff804318302b9 C:\WINDOWS\system32\ntoskrnl.exe
8 ntoskrnl.exe ObOpenObjectByNameEx + 0x1037 0xfffff80431e18c47 C:\WINDOWS\system32\ntoskrnl.exe
9 ntoskrnl.exe NtClose + 0xde 0xfffff80431e1df3e C:\WINDOWS\system32\ntoskrnl.exe
10 ntoskrnl.exe setjmpex + 0x7af8 0xfffff804319cde98 C:\WINDOWS\system32\ntoskrnl.exe
11 ntdll.dll NtClose + 0x14 0x7ffa5f77c244 C:\Windows\System32\ntdll.dll
12 kernel32.dll BasepConstructSxsCreateProcessMessage + 0x1332 0x7ffa5f55b392 C:\Windows\System32\kernel32.dll
13 kernel32.dll BaseDllReadWriteIniFile + 0xb4a 0x7ffa5f558d0a C:\Windows\System32\kernel32.dll
14 kernel32.dll BaseDllReadWriteIniFile + 0xed 0x7ffa5f5582ad C:\Windows\System32\kernel32.dll
15 kernel32.dll GetPrivateProfileStringA + 0x62 0x7ffa5f560f42 C:\Windows\System32\kernel32.dll
16 reaper.exe reaper.exe + 0x19f296 0x14019f296 C:\Program Files\REAPER (x64)\reaper.exe
17 reaper.exe reaper.exe + 0x2a5a19 0x1402a5a19 C:\Program Files\REAPER (x64)\reaper.exe
18 reaper.exe reaper.exe + 0x74d938 0x14074d938 C:\Program Files\REAPER (x64)\reaper.exe
19 user32.dll CallWindowProcW + 0x3bd 0x7ffa5eb5681d C:\Windows\System32\user32.dll
20 user32.dll SendMessageW + 0x38c 0x7ffa5eb55e2c C:\Windows\System32\user32.dll
21 user32.dll SendMessageA + 0x55 0x7ffa5eb69035 C:\Windows\System32\user32.dll
22 reaper.exe reaper.exe + 0x74e2de 0x14074e2de C:\Program Files\REAPER (x64)\reaper.exe
23 user32.dll CallWindowProcW + 0x3bd 0x7ffa5eb5681d C:\Windows\System32\user32.dll
24 user32.dll DispatchMessageW + 0x3cc 0x7ffa5eb563ec C:\Windows\System32\user32.dll
25 user32.dll UnionRect + 0x172 0x7ffa5eb64e82 C:\Windows\System32\user32.dll
26 ntdll.dll KiUserCallbackDispatcher + 0x24 0x7ffa5f77fdb4 C:\Windows\System32\ntdll.dll
27 ntoskrnl.exe KeUserModeCallback + 0x1e5 0xfffff80431e70085 C:\WINDOWS\system32\ntoskrnl.exe
28 win32kfull.sys EditionKeyEventLLHook + 0x1140 0xfffff30f74c7bb10 C:\WINDOWS\System32\win32kfull.sys
29 win32kfull.sys xxxUpdateInputHangInfo + 0x191d 0xfffff30f74ca519d C:\WINDOWS\System32\win32kfull.sys
30 win32kfull.sys xxxUpdateInputHangInfo + 0x1502 0xfffff30f74ca4d82 C:\WINDOWS\System32\win32kfull.sys
31 win32kfull.sys NtUserGetMessage + 0x8f8 0xfffff30f74ca1b18 C:\WINDOWS\System32\win32kfull.sys
32 win32kfull.sys NtUserCreateWindowEx + 0x223c 0xfffff30f74c497bc C:\WINDOWS\System32\win32kfull.sys
33 win32kfull.sys NtUserCreateWindowEx + 0x6a0 0xfffff30f74c47c20 C:\WINDOWS\System32\win32kfull.sys
34 ntoskrnl.exe setjmpex + 0x7af8 0xfffff804319cde98 C:\WINDOWS\system32\ntoskrnl.exe
35 win32u.dll NtUserCreateWindowEx + 0x14 0x7ffa5bf81f24 C:\Windows\System32\win32u.dll
36 user32.dll CreateWindowExW + 0x651 0x7ffa5eb48001 C:\Windows\System32\user32.dll
37 user32.dll CreateWindowExW + 0x244 0x7ffa5eb47bf4 C:\Windows\System32\user32.dll
38 user32.dll CreateWindowExA + 0x82 0x7ffa5eb6b552 C:\Windows\System32\user32.dll
39 reaper.exe reaper.exe + 0x74f819 0x14074f819 C:\Program Files\REAPER (x64)\reaper.exe
40 reaper.exe reaper.exe + 0x74cf4e 0x14074cf4e C:\Program Files\REAPER (x64)\reaper.exe
41 reaper.exe reaper.exe + 0x8fed17 0x1408fed17 C:\Program Files\REAPER (x64)\reaper.exe
42 reaper.exe reaper.exe + 0x8fedef 0x1408fedef C:\Program Files\REAPER (x64)\reaper.exe
43 kernel32.dll BaseThreadInitThunk + 0x14 0x7ffa5f567944 C:\Windows\System32\kernel32.dll
44 ntdll.dll RtlUserThreadStart + 0x21 0x7ffa5f74ce71 C:\Windows\System32\ntdll.dll
ajawamnet is offline   Reply With Quote
Old 08-13-2021, 08:50 AM   #21
ajawamnet
Human being with feelings
 
Join Date: Jun 2017
Posts: 172
Default

When I have all FX deleted - including all monitor FX - I get this in the IPR_MJ_ClOSE Procmon stack:

0 FLTMGR.SYS FltDecodeParameters + 0x1cfc 0xfffff804334c4a5c C:\WINDOWS\System32\drivers\FLTMGR.SYS
1 FLTMGR.SYS FltDecodeParameters + 0x1840 0xfffff804334c45a0 C:\WINDOWS\System32\drivers\FLTMGR.SYS
2 FLTMGR.SYS FltDecodeParameters + 0x13b2 0xfffff804334c4112 C:\WINDOWS\System32\drivers\FLTMGR.SYS
3 FLTMGR.SYS FltDecodeParameters + 0x119e 0xfffff804334c3efe C:\WINDOWS\System32\drivers\FLTMGR.SYS
4 ntoskrnl.exe IofCallDriver + 0x59 0xfffff80431827da9 C:\WINDOWS\system32\ntoskrnl.exe
5 ntoskrnl.exe ProbeForWrite + 0x19d 0xfffff80431e13e4d C:\WINDOWS\system32\ntoskrnl.exe
6 ntoskrnl.exe SeQueryInformationToken + 0xff0 0xfffff80431e22470 C:\WINDOWS\system32\ntoskrnl.exe
7 ntoskrnl.exe ObfDereferenceObjectWithTag + 0xc9 0xfffff804318302b9 C:\WINDOWS\system32\ntoskrnl.exe
8 ntoskrnl.exe ObOpenObjectByNameEx + 0x1037 0xfffff80431e18c47 C:\WINDOWS\system32\ntoskrnl.exe
9 ntoskrnl.exe NtClose + 0xde 0xfffff80431e1df3e C:\WINDOWS\system32\ntoskrnl.exe
10 ntoskrnl.exe setjmpex + 0x7af8 0xfffff804319cde98 C:\WINDOWS\system32\ntoskrnl.exe
11 ntdll.dll NtClose + 0x14 0x7ffa5f77c244 C:\WINDOWS\SYSTEM32\ntdll.dll
12 KERNEL32.DLL BasepConstructSxsCreateProcessMessage + 0x1332 0x7ffa5f55b392 C:\WINDOWS\System32\KERNEL32.DLL
13 KERNEL32.DLL BaseDllReadWriteIniFile + 0xb4a 0x7ffa5f558d0a C:\WINDOWS\System32\KERNEL32.DLL
14 KERNEL32.DLL BaseDllReadWriteIniFile + 0xed 0x7ffa5f5582ad C:\WINDOWS\System32\KERNEL32.DLL
15 KERNEL32.DLL GetPrivateProfileStringA + 0x62 0x7ffa5f560f42 C:\WINDOWS\System32\KERNEL32.DLL
16 reaper.exe reaper.exe + 0x19f296 0x14019f296 C:\Program Files\REAPER (x64)\reaper.exe
17 reaper.exe reaper.exe + 0x2a5a19 0x1402a5a19 C:\Program Files\REAPER (x64)\reaper.exe
18 reaper.exe reaper.exe + 0x74d938 0x14074d938 C:\Program Files\REAPER (x64)\reaper.exe
19 USER32.dll CallWindowProcW + 0x3bd 0x7ffa5eb5681d C:\WINDOWS\System32\USER32.dll
20 USER32.dll SendMessageW + 0x38c 0x7ffa5eb55e2c C:\WINDOWS\System32\USER32.dll
21 USER32.dll SendMessageA + 0x55 0x7ffa5eb69035 C:\WINDOWS\System32\USER32.dll
22 reaper.exe reaper.exe + 0x74e2de 0x14074e2de C:\Program Files\REAPER (x64)\reaper.exe
23 USER32.dll CallWindowProcW + 0x3bd 0x7ffa5eb5681d C:\WINDOWS\System32\USER32.dll
24 USER32.dll DispatchMessageW + 0x3cc 0x7ffa5eb563ec C:\WINDOWS\System32\USER32.dll
25 USER32.dll UnionRect + 0x172 0x7ffa5eb64e82 C:\WINDOWS\System32\USER32.dll
26 ntdll.dll KiUserCallbackDispatcher + 0x24 0x7ffa5f77fdb4 C:\WINDOWS\SYSTEM32\ntdll.dll
27 ntoskrnl.exe KeUserModeCallback + 0x1e5 0xfffff80431e70085 C:\WINDOWS\system32\ntoskrnl.exe
28 win32kfull.sys EditionKeyEventLLHook + 0x1140 0xfffff30f74c7bb10 C:\WINDOWS\System32\win32kfull.sys
29 win32kfull.sys xxxUpdateInputHangInfo + 0x191d 0xfffff30f74ca519d C:\WINDOWS\System32\win32kfull.sys
30 win32kfull.sys xxxUpdateInputHangInfo + 0x1502 0xfffff30f74ca4d82 C:\WINDOWS\System32\win32kfull.sys
31 win32kfull.sys NtUserGetMessage + 0x8f8 0xfffff30f74ca1b18 C:\WINDOWS\System32\win32kfull.sys
32 win32kfull.sys NtUserCreateWindowEx + 0x223c 0xfffff30f74c497bc C:\WINDOWS\System32\win32kfull.sys
33 win32kfull.sys NtUserCreateWindowEx + 0x6a0 0xfffff30f74c47c20 C:\WINDOWS\System32\win32kfull.sys
34 ntoskrnl.exe setjmpex + 0x7af8 0xfffff804319cde98 C:\WINDOWS\system32\ntoskrnl.exe
35 win32u.dll NtUserCreateWindowEx + 0x14 0x7ffa5bf81f24 C:\WINDOWS\System32\win32u.dll
36 USER32.dll CreateWindowExW + 0x651 0x7ffa5eb48001 C:\WINDOWS\System32\USER32.dll
37 USER32.dll CreateWindowExW + 0x244 0x7ffa5eb47bf4 C:\WINDOWS\System32\USER32.dll
38 USER32.dll CreateWindowExA + 0x82 0x7ffa5eb6b552 C:\WINDOWS\System32\USER32.dll
39 reaper.exe reaper.exe + 0x74f819 0x14074f819 C:\Program Files\REAPER (x64)\reaper.exe
40 reaper.exe reaper.exe + 0x74cf4e 0x14074cf4e C:\Program Files\REAPER (x64)\reaper.exe
41 reaper.exe reaper.exe + 0x8fed17 0x1408fed17 C:\Program Files\REAPER (x64)\reaper.exe
42 reaper.exe reaper.exe + 0x8fedef 0x1408fedef C:\Program Files\REAPER (x64)\reaper.exe
43 KERNEL32.DLL BaseThreadInitThunk + 0x14 0x7ffa5f567944 C:\WINDOWS\System32\KERNEL32.DLL
44 ntdll.dll RtlUserThreadStart + 0x21 0x7ffa5f74ce71 C:\WINDOWS\SYSTEM32\ntdll.dll
ajawamnet is offline   Reply With Quote
Old 08-13-2021, 08:52 AM   #22
karbomusic
Human being with feelings
 
karbomusic's Avatar
 
Join Date: May 2009
Posts: 29,260
Default

Thanks for that info, symbols are working well enough FYI...

Looks like a hang reading or writing to an ini file assuming this sticks here and never changes once hung. Relevant frames in bold below.

So we are waiting though at the filter driver level. That's what FLTMGR.SYS is in the top few frames. This is where drivers that inspect I/O packets to and from disk sit. You could run cmd.exe explicitly as administrator, then run this command:

FLTMC Instances

and post the results. This is mostly a sanity check so we can see which storage level filter drivers (such as AV) are active and inspecting IO packets. At any rate, this looks like a hang trying to read/write/open or close one of Reapers.ini files - again assuming this stack remains the same and this is where it is actually hung. We would need similar in process explorer to try to confirm if this is the thread that is hanging (because in process explorer the stack is live instead of a static snapshot).

Quote:
Originally Posted by ajawamnet View Post
When that wontclose_nofx.RPP hangs when I have 32 bit monitor FX loaded the IRP_MJ_CLOSE the stack for it in Procmon is:

0 FLTMGR.SYS FltDecodeParameters + 0x1cfc 0xfffff804334c4a5c C:\WINDOWS\System32\drivers\FLTMGR.SYS
1 FLTMGR.SYS FltDecodeParameters + 0x1840 0xfffff804334c45a0 C:\WINDOWS\System32\drivers\FLTMGR.SYS
2 FLTMGR.SYS FltDecodeParameters + 0x13b2 0xfffff804334c4112 C:\WINDOWS\System32\drivers\FLTMGR.SYS
3 FLTMGR.SYS FltDecodeParameters + 0x119e 0xfffff804334c3efe C:\WINDOWS\System32\drivers\FLTMGR.SYS
4 ntoskrnl.exe IofCallDriver + 0x59 0xfffff80431827da9 C:\WINDOWS\system32\ntoskrnl.exe
5 ntoskrnl.exe ProbeForWrite + 0x19d 0xfffff80431e13e4d C:\WINDOWS\system32\ntoskrnl.exe
6 ntoskrnl.exe SeQueryInformationToken + 0xff0 0xfffff80431e22470 C:\WINDOWS\system32\ntoskrnl.exe
7 ntoskrnl.exe ObfDereferenceObjectWithTag + 0xc9 0xfffff804318302b9 C:\WINDOWS\system32\ntoskrnl.exe
8 ntoskrnl.exe ObOpenObjectByNameEx + 0x1037 0xfffff80431e18c47 C:\WINDOWS\system32\ntoskrnl.exe
9 ntoskrnl.exe NtClose + 0xde 0xfffff80431e1df3e C:\WINDOWS\system32\ntoskrnl.exe
10 ntoskrnl.exe setjmpex + 0x7af8 0xfffff804319cde98 C:\WINDOWS\system32\ntoskrnl.exe
11 ntdll.dll NtClose + 0x14 0x7ffa5f77c244 C:\Windows\System32\ntdll.dll
12 kernel32.dll BasepConstructSxsCreateProcessMessage + 0x1332 0x7ffa5f55b392 C:\Windows\System32\kernel32.dll
13 kernel32.dll BaseDllReadWriteIniFile + 0xb4a 0x7ffa5f558d0a C:\Windows\System32\kernel32.dll
14 kernel32.dll BaseDllReadWriteIniFile + 0xed 0x7ffa5f5582ad C:\Windows\System32\kernel32.dll

15 kernel32.dll GetPrivateProfileStringA + 0x62 0x7ffa5f560f42 C:\Windows\System32\kernel32.dll
16 reaper.exe reaper.exe + 0x19f296 0x14019f296 C:\Program Files\REAPER (x64)\reaper.exe
17 reaper.exe reaper.exe + 0x2a5a19 0x1402a5a19 C:\Program Files\REAPER (x64)\reaper.exe
18 reaper.exe reaper.exe + 0x74d938 0x14074d938 C:\Program Files\REAPER (x64)\reaper.exe
19 user32.dll CallWindowProcW + 0x3bd 0x7ffa5eb5681d C:\Windows\System32\user32.dll
20 user32.dll SendMessageW + 0x38c 0x7ffa5eb55e2c C:\Windows\System32\user32.dll
21 user32.dll SendMessageA + 0x55 0x7ffa5eb69035 C:\Windows\System32\user32.dll
22 reaper.exe reaper.exe + 0x74e2de 0x14074e2de C:\Program Files\REAPER (x64)\reaper.exe
23 user32.dll CallWindowProcW + 0x3bd 0x7ffa5eb5681d C:\Windows\System32\user32.dll
24 user32.dll DispatchMessageW + 0x3cc 0x7ffa5eb563ec C:\Windows\System32\user32.dll
25 user32.dll UnionRect + 0x172 0x7ffa5eb64e82 C:\Windows\System32\user32.dll
26 ntdll.dll KiUserCallbackDispatcher + 0x24 0x7ffa5f77fdb4 C:\Windows\System32\ntdll.dll
27 ntoskrnl.exe KeUserModeCallback + 0x1e5 0xfffff80431e70085 C:\WINDOWS\system32\ntoskrnl.exe
28 win32kfull.sys EditionKeyEventLLHook + 0x1140 0xfffff30f74c7bb10 C:\WINDOWS\System32\win32kfull.sys
29 win32kfull.sys xxxUpdateInputHangInfo + 0x191d 0xfffff30f74ca519d C:\WINDOWS\System32\win32kfull.sys
30 win32kfull.sys xxxUpdateInputHangInfo + 0x1502 0xfffff30f74ca4d82 C:\WINDOWS\System32\win32kfull.sys
31 win32kfull.sys NtUserGetMessage + 0x8f8 0xfffff30f74ca1b18 C:\WINDOWS\System32\win32kfull.sys
32 win32kfull.sys NtUserCreateWindowEx + 0x223c 0xfffff30f74c497bc C:\WINDOWS\System32\win32kfull.sys
33 win32kfull.sys NtUserCreateWindowEx + 0x6a0 0xfffff30f74c47c20 C:\WINDOWS\System32\win32kfull.sys
34 ntoskrnl.exe setjmpex + 0x7af8 0xfffff804319cde98 C:\WINDOWS\system32\ntoskrnl.exe
35 win32u.dll NtUserCreateWindowEx + 0x14 0x7ffa5bf81f24 C:\Windows\System32\win32u.dll
36 user32.dll CreateWindowExW + 0x651 0x7ffa5eb48001 C:\Windows\System32\user32.dll
37 user32.dll CreateWindowExW + 0x244 0x7ffa5eb47bf4 C:\Windows\System32\user32.dll
38 user32.dll CreateWindowExA + 0x82 0x7ffa5eb6b552 C:\Windows\System32\user32.dll
39 reaper.exe reaper.exe + 0x74f819 0x14074f819 C:\Program Files\REAPER (x64)\reaper.exe
40 reaper.exe reaper.exe + 0x74cf4e 0x14074cf4e C:\Program Files\REAPER (x64)\reaper.exe
41 reaper.exe reaper.exe + 0x8fed17 0x1408fed17 C:\Program Files\REAPER (x64)\reaper.exe
42 reaper.exe reaper.exe + 0x8fedef 0x1408fedef C:\Program Files\REAPER (x64)\reaper.exe
43 kernel32.dll BaseThreadInitThunk + 0x14 0x7ffa5f567944 C:\Windows\System32\kernel32.dll
44 ntdll.dll RtlUserThreadStart + 0x21 0x7ffa5f74ce71 C:\Windows\System32\ntdll.dll
You might look in procmon to see if you can deciper which ini file is being accessed - as there may be a Create or CloseFile operation near the above ^that event which may tell us which file.

Also @Justin since he likely knows exactly what this stack is doing.
__________________
Music is what feelings sound like.

Last edited by karbomusic; 08-13-2021 at 09:08 AM.
karbomusic is offline   Reply With Quote
Old 08-15-2021, 10:22 AM   #23
ramses
Human being with feelings
 
Join Date: Jul 2009
Posts: 1,231
Default

For me the lastest dev release fixed it. v6.34+dev0814.
ramses is offline   Reply With Quote
Old 08-15-2021, 01:05 PM   #24
Gass n Klang
Human being with feelings
 
Gass n Klang's Avatar
 
Join Date: Nov 2015
Location: Cologne
Posts: 1,636
Default

Quote:
Originally Posted by ramses View Post
For me the lastest dev release fixed it. v6.34+dev0814.
Yes. It takes a while (20 Seconds? on "Initializing") but it opens.
__________________
https://juliusgass.de
Gass n Klang is online now   Reply With Quote
Old 08-17-2021, 03:17 AM   #25
Gass n Klang
Human being with feelings
 
Gass n Klang's Avatar
 
Join Date: Nov 2015
Location: Cologne
Posts: 1,636
Default

ok I think the long loading time was due to the complex project. Seems to work. Whatever changed: Thank you devs! This helps a lot.
__________________
https://juliusgass.de
Gass n Klang is online now   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 02:02 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.