Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
AppHangB1 errors when launching latest GIT builds
#11
OrdosAlpha:
Do you think you can debug this? We need to see where it hangs in a debugger.
Reply

Sponsored links

#12
I seem to be in the same boat as OrdosAlpha(just tested with 561 & 563; 561 runs fine but 563 doesn't). I don't know how to work the debugger, but the last thing I see in emuLog.txt is always "Reserving memory for recompilers..." and this is what I see after the run wizard finishes: https://dl.dropboxusercontent.com/u/3073...2crash.png
The log window doesn't even render in launches not involving the wizard.
Reply
#13
(09-21-2014, 06:32 PM)OrdosAlpha Wrote: The last GIT build that atually works was 1.2.1-561-g08dc8b4 and that was made available on the 6th of this month.

This reminds me, who do I speak to about changing the version number in the .zip file (and the folder contained inside) from 1.2.1 to 1.3.0?
[Image: pNm13X9.gif]
Windows 10 Pro x64 | Intel Core i7-4790K @ 4.00 GHz | PowerColor R9 290X 4GB | G.SKILL 16GB (4x4GB) DDR3 1600 RAM | Samsung 850 EVO 250 GB SSD | Seagate ST3000DM001 3TB HDD

CPU Intensive Games
GPU Intensive Games
Games that don't need a strong CPU
Reply
#14
(09-25-2014, 06:27 PM)karasuhebi Wrote: This reminds me, who do I speak to about changing the version number in the .zip file (and the folder contained inside) from 1.2.1 to 1.3.0?

We've already mentioned it to the devs. Orphis (who manages the buildbot) is the one that needs to change something I think.
[Image: XTe1j6J.png]
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Reply
#15
(09-25-2014, 01:55 PM)Rhimrifer Wrote: I seem to be in the same boat as OrdosAlpha(just tested with 561 & 563; 561 runs fine but 563 doesn't). I don't know how to work the debugger, but the last thing I see in emuLog.txt is always "Reserving memory for recompilers..." and this is what I see after the run wizard finishes: https://dl.dropboxusercontent.com/u/3073...2crash.png
The log window doesn't even render in launches not involving the wizard.

Exactly what I'm getting. If you leave it for about 5 minutes, then it will eventually load the pcsx2 window, and everything works normally.
Reply
#16
(09-25-2014, 11:28 AM)rama Wrote: OrdosAlpha:
Do you think you can debug this? We need to see where it hangs in a debugger.

Didn't notice this post on my last visit. Mind you, I was pressed for time at the time of the post, and in the period since due to having to deal with real life stuff.

Anyway, I'd be willing to help debug this, would love to know what's causing the delayed loading of the emulator. Just need to know what you need me to do, and I'll give it a go if I'm able to.
Reply




Users browsing this thread: 1 Guest(s)