Unzipping in the plugin crashing the browser

[Lindon]

@DanH said in Unzipping in the plugin crashing the browser:

@Lindon did you make a debug standalone?

nope _ Im not entirely clear how I go about doing that...

[DanH]

@Lindon open the autogeneratedProject in your build folder so you can open the project in Xcode, then choose to build in Running rather than Profiling.

When it's built (it should say debug after the app name) run it, then make it crash and look at the crash report. Post findings here...

[Lindon]

@DanH said in Unzipping in the plugin crashing the browser:

@Lindon open the autogeneratedProject in your build folder so you can open the project in Xcode, then choose to build in Running rather than Profiling.

When it's built (it should say debug after the app name) run it, then make it crash and look at the crash report. Post findings here...

thanks well Im on windows but Im sure its similar...

[DanH]

@Lindon I guess, not so sure where the crash reports are and how readable they are...

[Lindon]

@DanH said in Unzipping in the plugin crashing the browser:

@Lindon I guess, not so sure where the crash reports are and how readable they are...

yeah me neither - I'v opened projucer loaded the project into Visual Studio selected

Debug - started it - the app has opened, I've run it and its crashed (eventually) but I have no idea what im looking at now...

[Lindon]

@Lindon trying it again and now nothing even starts...can anyone give me a clue how to start debugging this with Visual Studio?

[DanH]

@Lindon what happens if you make it crash while it's actually open in VS? It shouldn't crash but might point you in the right direction?

[Lindon]

@DanH it wont even open in VS!!!

I open projucer File>Save Project and open in IDE

VS opens, I select Debug>Start Debugging(F5)

I get thisL:

No sign of the app actually starting..

[Lindon]

@Lindon ok I stepped past all these breakpoints got it to loaad and run and got this when it crashes:

some sort of read access violation???

[DanH]

@Lindon I’m in the pub (suggest you do the same ). But what size is the file you’re trying to unzip?

[Lindon]

@DanH just back from the pub --- 1.4Gb...

[DanH]

@Lindon ok, unlikely to be that then. Did you send your code to @d-healey to look at? Feel free to send my way as well.

[d.healey]

@Lindon Follow the call stack

Click the line that mentions the extractZipFile function and see what's going on.

[Lindon]

@d-healey ok so doing that shows me this:

So there's a problem with the thread, and I have this in my pre-processors:

Would that make any difference?

[Lindon]

@Christoph-Hart --- -you will want to see this answer I think:

..aaaaaand the answer is yes. If I set all the preprocessor commands I need to use the unlocker to off(zero) then the unzip code works fine.

So I need the unlocker and I need the unzipper - How do I proceed?

[DanH]

This post is deleted!

[DanH]

@Lindon I actually use a separate standalone app as part of the installation process. It downloads the samples, unzips and installs them, creates the link file, and can handle the license activation too. So when the user opens the actual plugin for the first time they don't have anything to do, it works right off the bat.

Potentially a way around this.

[Lindon]

@DanH Thanks but thats not possible with the distribution partner we are using.

[DanH]

@Lindon will users have to download the zip file when they open the plugin for the first time or will it already have been downloaded?

[Lindon]

@DanH the plug-in does everything...