Projucer crash report


#1

Just got a crash using Projucer while trying out the GUI Editor (brand new user).
What I did was adding an image to a GUI project, got asked for a resource, added the resource, tried to go to Code page, after that - crash.

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	Projucer.exe
  Application Version:	4.3.1.0
  Application Timestamp:	58c83972
  Fault Module Name:	Projucer.exe
  Fault Module Version:	4.3.1.0
  Fault Module Timestamp:	58c83972
  Exception Code:	c0000005
  Exception Offset:	00000000000e3f95
  OS Version:	6.3.9600.2.0.0.256.48
  Locale ID:	1033
  Additional Information 1:	bb62
  Additional Information 2:	bb6241e6930a32c3527fbb2dfb3ec221
  Additional Information 3:	b416
  Additional Information 4:	b41683e81ff557c5e670b0c6eadcd6ac

Win 8.1, latest JUCE

edit:
Not reproduceable so far when trying again


#2

i had some crashes too in the projucer, mostly in the gui component editor, when editing components sizes and path drawing code. didn’t have the time to debug those tho… but it seems the component editor is not receiving updates or fixes


#3

Thanks kraken.

It’s not super critical to me currently as I just play around and try stuff out to get familiar with JUCE, but just got another crash, also doing things in the GUI editor.

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	Projucer.exe
  Application Version:	4.3.1.0
  Application Timestamp:	58c83972
  Fault Module Name:	Projucer.exe
  Fault Module Version:	4.3.1.0
  Fault Module Timestamp:	58c83972
  Exception Code:	c0000005
  Exception Offset:	00000000000c9115
  OS Version:	6.3.9600.2.0.0.256.48
  Locale ID:	1033
  Additional Information 1:	9ef5
  Additional Information 2:	9ef524de11bf3d22e3c59c9ea14ba327
  Additional Information 3:	731c
  Additional Information 4:	731c6c43f8f02e88189dc0bf37f3480b

#4

We’re not actively updating it but we’ll certainly fix crashes!

The stack traces above aren’t much use though…


#5

Anything I can provide that’s more helpful if it happens again ?


#6

Well yes, if you run the debug build, send us a stack trace!