Crash clicking empty header of VP Explorer column - Fixed in VP14

NickHope wrote on 4/9/2015, 1:05 AM

As raised by Christian de Godzinsky in this thread, Vegas Pro crashes when one clicks in the empty area at the top of the Explorer window, to the right of the active columns.

See http://dl.dropboxusercontent.com/u/21489814/Vegas-Explorer-crash-VP12-13.png


I have tested this with VP12 and VP13 build 444. Both have the problem. It does not happen in VP10.0e, where the top of the empty column is rendered like the active columns (i.e. not "empty").

See http://dl.dropboxusercontent.com/u/21489814/Vegas-explorer-VP10.png


I will submit a bug report. It would be useful if some more users could verify this.

Comments

ChristoC wrote on 4/9/2015, 1:29 AM

Confirmed!
Peter100 wrote on 4/9/2015, 1:50 AM
I confirm this error in VP 13 build 428. However in my cease you have to try very hard to cause the error. First you have switch the view to "details". In details mode all the colums fill the full width of the window. So in my case, you need to decrease width of the side colum to reveal the unpopulated header.

Edit: You can reveal the unpopulated part of the table also by scaling the window width.
xberk wrote on 4/9/2015, 11:19 AM
I confirm too. True. This shouldn't happen. But as a practical matter it's not something that I've ever done. I use detail mode all the time but mostly I would never see a blank header like that much less click on it. Still. It's a bug.

Paul B .. PCI Express Video Card: EVGA VCX 10G-P5-3885-KL GeForce RTX 3080 XC3 ULTRA ,,  Intel Core i9-11900K Desktop Processor ,,  MSI Z590-A PRO Desktop Motherboard LGA-1200 ,, 64GB (2X32GB) XPG GAMMIX D45 DDR4 3200MHz 288-Pin SDRAM PC4-25600 Memory .. Seasonic Power Supply SSR-1000FX Focus Plus 1000W ,, Arctic Liquid Freezer II – 360MM .. Fractal Design case ,, Samsung Solid State Drive MZ-V8P1T0B/AM 980 PRO 1TB PCI Express 4 NVMe M.2 ,, Wundiws 10 .. Vegas Pro 19 Edit

NickHope wrote on 4/9/2015, 11:44 AM
Wow! I had a reply already from SCS support. Same day! It includes this:

"I have reproduced the crash you've experienced. I have escalated the issue to our development and QA teams, and will update you when I hear back from them. In the meantime, I will set this incident to Development status so it remains open."

But it's not all roses. Still haven't had an answer to my last bug report, submitted on 8th March.
NormanPCN wrote on 4/9/2015, 2:09 PM
I have gotten a bug report quickly confirmed by support and entered into the database and two years later and V12 goes to V13, and...apparently not worth fixing.
Cliff Etzel wrote on 4/9/2015, 2:58 PM
I guess this is yet another glaring example of why I halted my move to Vegas Pro. It's the ongoing issues like this that just feels as though Vegas can''t seriously be ' considered by many professional post production people as a viable tool. I agree no app is perfect, but when you have glaring bugs as simple as this still residing in the code, you have to wonder how many corners are being cut.

Vegas Pro needed a total rewrite 2 generations back, but it's probably too late given the nature of the market today.

One can only hope VP14 is something more than an added features upgrade using the same underlying programming.

I hope when VP14 is announced at NAB that it's groundbreaking.
john_dennis wrote on 4/9/2015, 3:22 PM
I tested this on Vegas Pro 12 and it also failed on two different machines. I've sent failure data when prompted. Vegas Pro 11 didn't fail. The behavior probably surfaced in Vegas Pro 12.

My main system:
Motherboard: Asus X99-AII
CPU: Intel i7-6850K
GPU: Sapphire Radeon RX480-8GB
RAM: Corsair Dominator (4 x 4 GB) DDR4 2400
Disk O/S & Programs: Intel SSD 750 (400 GB)
Disk Active Projects: 1TB & 2TB WD BLACK SN750 NVMe Internal PCI Express 3.0 x4 Solid State Drives
Disk Other: WD Ultrastar/Hitachi Hard Drives: WDBBUR0080BNC-WRSN, HGST HUH728080ALE600, 724040ALE640, HDS3020BLA642
Case: LIAN LI PC-90 Black Aluminum ATX Full Tower Case
CPU cooling: Corsair Hydro series H115i
Power supply: SeaSonic SS-750KM3 750W 80 PLUS GOLD Certified Full Modular Active PFC Power Supply
Drive Bay: Kingwin KF-256-BK 2.5" and 3.5" Trayless Hot Swap Rack with USB 3
Sound card: Crystal Sound 3 on motherboard. Recording done on another system.
Primary Monitor: Asus ProArt PA248q (24" 1920 x 1200)
O/S: Windows 10 Pro 22H2, Build 19045.2130

Camera: Sony RX10 Model IV

https://www.youtube.com/user/thedennischannel

OldSmoke wrote on 4/9/2015, 4:15 PM
I can confirm this "bug" but I also wonder why some would click there?

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

NickHope wrote on 4/9/2015, 10:50 PM
A couple of hours later I got a reply that included this:

"I've heard back from QA regarding this crash. It has been recorded in our database as a bug. Thanks again for bringing this to our attention."
Erni wrote on 4/10/2015, 8:27 AM
Who in the hell needs make click in this site?

Yes, ii is a bug, but...

Erni
NickHope wrote on 4/10/2015, 8:55 AM
Who in the **** needs to whinge about the discussion of a Vegas bug?

If it doesn't concern you Erni, then please just move along.
OldSmoke wrote on 4/10/2015, 9:02 AM
Nick

I am with Erni on this one. I do acknowledge that it is a bug but again, why is anyone clicking there during a normal editing session? I would have never found it in a million years.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

NickHope wrote on 4/10/2015, 9:15 AM
Maybe it's connected to other bugs like the file renaming bug. Who knows?

Anyway it's been reported, and logged as a bug. I don't see the need to spend effort whinging about that. Just let it go.
Erni wrote on 4/10/2015, 10:32 AM
OMG. I'm very sorry Nick :)

I don't know what is your "bug" concept.
It's very different of mine.

Cheers

Erni
winrockpost wrote on 4/10/2015, 2:43 PM
one of those things that would be a sudden crash out of nowhere, seemingly random....in the middle of an edit and clicking the empty header without even realizing it....that's why it is a bug worth fixing...in my opinion
videoITguy wrote on 4/10/2015, 5:39 PM
Usually the granularity of programming a user interface in most hard-coded apps like VegasPro - does not foresee this kind of issue becoming a bug. But as user interfaces get more complicated the granularity of the UI does increase exponentially. As some users have testified this was not a problem in earlier programming - so now it rears up as a potential.

This is quite unlike the granularity of coding web apps - for example browsers - their UI suffers very easy interference from the host OS, infections by adware and the like which make identifying a bug of this type a bit more dicey.

Should not be so much in a hard-coded app.
john_dennis wrote on 4/10/2015, 8:25 PM
As a somewhat disinterested party who verified the finding of other users, I was dispassionate and described this as a "behavior" and not a bug. This is primarily because I seldom use the Vegas Explorer and had to undock the Explorer so I could find an empty position to do the test.

In a more clinical moment I'll describe my thoughts on the matter:

1) At least one user has stumbled on this and lost the use of Vegas Pro and any un-saved edits until the program was restarted.

2) According to the problem report it is an unmanaged exception. The team at SCS has had two numbered releases to find and handle this exception.

3) The exception, no matter how unlikely or mundane, should be handled without ending the session.

My personal, non-professional perception is that this exception could be handled quite well by just doing nothing until the user woke up and clicked on a part of the screen that is meaningful.

My main system:
Motherboard: Asus X99-AII
CPU: Intel i7-6850K
GPU: Sapphire Radeon RX480-8GB
RAM: Corsair Dominator (4 x 4 GB) DDR4 2400
Disk O/S & Programs: Intel SSD 750 (400 GB)
Disk Active Projects: 1TB & 2TB WD BLACK SN750 NVMe Internal PCI Express 3.0 x4 Solid State Drives
Disk Other: WD Ultrastar/Hitachi Hard Drives: WDBBUR0080BNC-WRSN, HGST HUH728080ALE600, 724040ALE640, HDS3020BLA642
Case: LIAN LI PC-90 Black Aluminum ATX Full Tower Case
CPU cooling: Corsair Hydro series H115i
Power supply: SeaSonic SS-750KM3 750W 80 PLUS GOLD Certified Full Modular Active PFC Power Supply
Drive Bay: Kingwin KF-256-BK 2.5" and 3.5" Trayless Hot Swap Rack with USB 3
Sound card: Crystal Sound 3 on motherboard. Recording done on another system.
Primary Monitor: Asus ProArt PA248q (24" 1920 x 1200)
O/S: Windows 10 Pro 22H2, Build 19045.2130

Camera: Sony RX10 Model IV

https://www.youtube.com/user/thedennischannel

Christian de Godzinsky wrote on 4/11/2015, 9:11 AM
Hi,

Thank you Nick for reporting this to SCS. I agree that this bug is not a showstopper and can be avoided when you know about it. However, bugs at this level should simply not exist or should not be possible to easily generate - assuming the underlying code is well structured and professionally written. Exception handling is routine.

I understand that SCS has probably been busy fixing more important bugs, but they are lagging behind even there. Build 444 was little of a disappointment, many known issues still waiting to be fixed... I would give much to have access to the SCS' "to do" list....

Since NAB is close I thing the next bug fix will probably have a price tag on it.

And tell me - how many other applications have you experienced where clicking an empty column in a list kills the application... ?

Cheers

Christian

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

Erni wrote on 4/11/2015, 9:37 AM
Storm in a tea cup.

Tormenta en un vaso de agua, le decimos por aquí.

Relax, (and no click in the hidden area) :D

Erni
NickHope wrote on 9/20/2016, 3:04 AM

This bug is fixed in VEGAS Pro 14.0 (Build 161). Thanks!