However once the program reaches the line:
dataiterator = iter(trainloader)
It crashes and asks me twice whether I want to kill the python program(Like I pressed the close window button). The program is then unable to continue and hangs, this problem still persists after changing the:
iter()
to a for loop:
for image, label in trainloader
It always crashes the program. Additionally every time it asks to close it leaves a python3 program running in the background and they each use about 350MB. I am using linux mint 18.1 with a lenovo thinkpad x230. Has anybody come across this error before?
Hi, I just turned on the Event Driven Loader for my project to take advantage of the faster loading times. After I cook and run the game, I get a hard crash upon game startup. The log file says that there are cycle nodes with some UMG widgets. ...
Just make sure that in the player pawn or in some other BP thats definitely used in the game at least one function from any of the BPFunctionLibraries is called, so that the BPFunctionLibraries are definitely packaged.
I did read over the previous question. I wanted to make sure that you were experiencing the same issue. After testing I found that this is working as intended. The issue is that an infinite loop is created and causes an fatal error during packaging. This is not an intended workflow. I hope that this information helps.
Hi Rudy, I think you did not understand the issue. There is no infinite loop in the code itself, its a bug with the event driven loader. If you disable that, packaging works correctly. If you enable blueprint nativization, packaging also works correctly. Only event driver loader enabled and blueprint nativization disabled causes this issue.
After further testing I was able to reproduce this issue on our end (without an infinite loop), I have written up a report and I have submitted it to the developers for further consideration. I have provided a link to the public tracker. Please feel free to use the link provided for future updates.
My forge client crashes after the FML Early Loading Process finishes. I have reinstalled forge, minecraft, and before doing both of those removed all mods to see if those were the problems. Nothing seems to be fixing and I just got into a modded server with friends the other day so It's very frustrating.
Here's the crash report if that helps
Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:
When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.
When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.
The tutorial had a while loop in the process function but that was even worse and resulted in the game freezing for the entire loading and the loading bar not updating, not just when the scene is added.
Inherits: RefCounted< Object A unit of execution in a process. Description: A unit of execution in a process. Can run methods on Object s simultaneously. The use of synchronization via Mutex or Sem...
The thing is that the ResourceInteractiveLoader returned from ResourceLoader.load_interactive() is not a background loader, it is just interactive, that is, it can break up loading in steps instead of doing all steps at once, but each step is synchronous and on the same thread as the caller. If you have one resource that has only one load step, but that load step takes 5 seconds, then using the interactive loader has no difference from just using the built in load() function.
I dont know if trying the opencomposite site wide installer (aero) on my system initially did this or not, but, i also re-clicked steamvr in it to set things back and did the per game install. However, now when i try to launch MSFS (i didnt install the dll there for opencomposite anyway), MSFS crashes with openxr_loader.dll errors in event viewer.
Then after 2 weeks there was the issue with the order that I started everything, and then extreme stuttering. So I worked out it was SteamVR after some other programs updated, and then a week later SteamVR updated when I started it, and MSFS was good. But the order of starting everything was still important. It worked for 3 days.
So I tried Opencomposite, and it worked, solved the stuttering. Even though I had MSFS on a drive of its own, and there was no .dll file placed in the folder. So I did something, it did nothing, but there was a result. Also, starting order was important still.
I'm trying to replay DAO, but every time I start it up and click start new game it goes to the loading screen and crashes. I have the Ultimate Edition and I have no mods installed. I have also tried repairing the game, uninstall and reinstall, setting the graphics to a lower setting and have tried playing it with affinity set to 1 core.
I'm not super tech-savvy but I'll try to help anyway. Have you tried the basic troubleshooting steps like updating the drivers, making sure an anti-virus is not blocking the game, running as admin, etc? Also, are you using Windows 10? If so, it's worth trying to run the game in compatibility mode.
I have the same issue now.. But I dont think they will answer since its from2015. If you found the solution or the files, can u please tell me? I recently bought Awakening (first had dao), now everytime I want to start a new game on Awakening (also DAO), the game will crash while loading. "Load game" and "resume" work without crashing but new game keeps crashing, I never played awakening before so I really want to play it....
I bought a new PC with quite decent speccs. So I turned up graphic settings to the max. And the crashes started in Denerim. I stumbled over this thread and they were right: after tuning down those graphic settings to medium, I was able to load again my save games. Maybe you can try this.
I got a file with a flat data table. I have built a dashboard based on pivot tables & charts. For some reason with the recent addition of some data fields, upon opening the XLSX it shows loading "Data Model".
Yep, it doesn't even crashes, excel just turns off. I already tried disabling all ADD-ins, but still no results.
There was one thing which helped. I restored the excel file 3 days back and it worked fine, but here is the catch. I uploaded that file back to sharepoint and still the same problem happened. The only way for now to use it is Online version
As you said, I think it's a bug
@athalekar
I have this exact same problem. Any fix yet? I found I can upload the file to msteams download then open fine. But if I upload to msteam, then open and use the file then download, then try to open it force closes while loading the data model @eligaliokas any ideas anyone how to fix this? Or what could be wrong? This happened after adding additional columns to a table. And adding charts to a dashboard.
@GGGG670 I cannot figure out why it is crashing as there is no error, no message nor any indication of what is causing a crash. I am not stuck as it is working fine when I open it online as the file is placed in One Drive. I am trying to fix data models, pivot tables and whatnot to check what can fix the crash. So far no luck.
@athalekar I've been having this problem also and over the last few days have tried various remedies mentioned here an elsewhere, and tried different orders or ways of doing things. Here is what finally seems to work for me:
I'm having a hard time reproducing this issue.
The crash report also looks totally unrelated to the RM (it failed to fetch the list of available monitors), however other reports indicate that it does indeed have something to do with the RM (and may be OSX specific which would explain my difficulties reproducing it).
Is this you or is this another independent report of the same issue?
Another report on the forum has since been deleted without explanation, so if you find a workaround (as they might have), please don't just delete your thread but instead provide as much info about the workaround as possible. That'll help both, other people having the same issue and us in potentially narrowing it down / reproducing it.
No that's not me.
I can give you an interesting thing tho...MultiMC has the same problem, yet actually seems to ignore the error and continues loading. Replay Mod is unable to start a recording when loading into a world though. Maybe there's something useful in there.
Here are the logs for that version:
The error in the log of both MultiMC and non-MultiMC is totally fine and expected and shouldn't be related to the crash itself. Interesting that it doesn't crash with MultiMC though, that could mean that it's a fabric or vanilla bug which is always there but RM does something to trigger it.
Edit: It could also explain why I'm having issues reproducing the issue (I'm haven't been using the vanilla launcher in years). I'll see if I can install and reproduce it tomorrow.
The error you're getting instead seems like a separate thing. I've fixed something similar in -b2. Could you try updating to -b3 (or -b2 if you need to stay on 1.14.2) and see if that solves it?
User53276B3 crashes with what looks like the same error. Had also updated Fabric and API.
Is this still on MultiMC?
The error I've fixed in -b2 is similar to the one you got on MultiMC causing the recording to fail.
I still have no idea why it isn't working with the vanilla launcher (and won't be looking into that before tomorrow).