8000 3.14 · Issue #43 · dolkensp/unp4k · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
8000

3.14 #43

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

8000
Jump to bottom
Open
snowboundmage2 opened this issue Aug 13, 2021 · 8 comments
Open

3.14 #43

snowboundmage2 opened this issue Aug 13, 2021 · 8 comments

Comments

@snowboundmage2
Copy link
snowboundmage2 commented Aug 13, 2021 •
edited
Loading

don't think unp4kGUI.exe is compatible, only gets a few files then crashes
@peter-dolkens
Copy link
Member

Have you made sure to download the latest release?

I'm not getting any issues in my testing.

@peter-dolkens
Copy link
Member

Also check you have space to extract the files you have requested.

If you haven't provided a filter, then you need around 120GB of space to extract the p4k file.

image

@Blue-0xEF
Copy link
Blue-0xEF commented Sep 17, 2021 via email

@AusKarlos87
Copy link
AusKarlos87 commented Sep 24, 2021 •
edited
Loading

Im having some issues with it extracting some files as well. It seems a fresh download of 3.14 works fine, but any pack file that was a fresh download from before 3.12 (and patched all the way to 3.14) seems to crash unp4k frequently.
The cli version seems to just skip over the files where the GUI version crashes.

Do you have any debugging flags that can be set to dump the std to a file?

@peter-dolkens
Copy link
Member
peter-dolkens commented Sep 24, 2021 via email

@sofyanet
Copy link
sofyanet commented Dec 6, 2021 •
edited
Loading

Hi,

I don't mean to high jack this issue ticket but I thought my problem might be related. I'm having issues with the GUI version. It does start analyzing the .p4k file then hangs after 98.66% completed and eventually crashes.

image

However, I had no issue unpacking the archive using the non GUI version. After running the GUI version through debug in VS, it appears that I hit a memory limitation:

System.OutOfMemoryException
HResult=0x8007000E
Message=Une exception de type 'System.OutOfMemoryException' a été levée.
Source=PresentationCore
Arborescence des appels de procédure :
à System.Windows.Media.Animation.TimeManager.Tick()
à System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
à System.Windows.Media.MediaContext.AnimatedRenderMessageHandler(Object resizedCompositionTarget)
à System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
à System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
à System.Windows.Threading.DispatcherOperation.InvokeImpl()
à System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
à MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
à System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
à MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
à System.Windows.Threading.DispatcherOperation.Invoke()
à System.Windows.Threading.Dispatcher.ProcessQueue()
à System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
à MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
à MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
à System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
à System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
à System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
à MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
à MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
à System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
à System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
à System.Windows.Application.RunDispatcher(Object ignore)
à System.Windows.Application.RunInternal(Window window)
à System.Windows.Application.Run(Window window)
à unp4k.gui.App.Main()

image

My system runs on 16 GB + 32 GB of paging.

Hope this helps.

@Stryxus
Copy link
Stryxus commented Dec 6, 2021 •
edited
Loading

@sofyanet Yes, this is most likely due to so many UI elements being created and stored into memory before actually being rendered. This will be fixed when myself and/or peter get a chance to start on the new MAUI GUI. (I rewrote a large chunk of unp4k/unforge which is just awaiting peter's approval and possible release although, the GUI in it had to be removed for the time being)

feature/net6

@sofyanet
Copy link
sofyanet commented Dec 7, 2021

@Stryxus Thank you for all those information.

@sofyanet sofyanet mentioned this issue Dec 16, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@peter-dolkens @Stryxus @Blue-0xEF @AusKarlos87 @sofyanet @snowboundmage2
0